|
From: | Brent W. Baccala |
Subject: | Re: kernel panic in gsync_wait |
Date: | Thu, 3 Nov 2016 14:12:41 -1000 |
"Brent W. Baccala" <cosine@freesoft.org> writes:
> Even if I'm right about the nature of this bug, I don't understand gnumach
> well enough to know how a task should access another task's memory.
vm_copy apparently supports such access; code from there could be
reused. But if rpctrace uses gsync_wait on the address space of
another task and the page has been paged out, then the call could
end up blocking for the pager, and I don't think you want that.
Could gsync_wait be removed from gnumach.defs and replaced with
only a trap that does not take a task_t parameter and cannot be
intercepted by rpctrace?
[Prev in Thread] | Current Thread | [Next in Thread] |