Ross Lagerwall writes ("Re: [PATCH for-4.10] libs/evtchn: Remove active handler
on clean-up or failure"):
> Now that I look at it, a similar scenario can happen during open. Since
> the handle is registered before it is actually opened, a concurrent
> xentoolcore_restrict_all() will try to restrict a handle that it not
> properly set up.
I think this is not a problem because the handle has thing->fd = -1.
So the restrict call will be a no-op (or give EBADF).
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
