|From:||Brent W. Baccala|
|Subject:||Re: behavior of NO SENDERS notifications when receive rights move|
|Date:||Tue, 4 Oct 2016 18:19:58 -1000|
"Brent W. Baccala" <email@example.com> writes:
> Now I'm wondering - how would DEAD NAME notifications be handled? rpctrace
> would want to transfer send rights with the DN notifications attached (so
> it could wrap them both), but my experience, and my understanding of the
> Mach documentation, is that moving a send right with a DN request triggers
> a PORT DELETED notification, which is not what we would want.
Before rpctrace moves the send right from the target task, it
could call mach_port_request_notification to cancel the dead-name
notification request. This call returns the send-once right to
which the notification would have been sent. After rpctrace has
moved the rights, it could restore the notification request,
now with a wrapped send right and a wrapped send-once right.
|[Prev in Thread]||Current Thread||[Next in Thread]|