On Tue 27 Oct 2009 at 07:03PM, Edward Pilatowicz wrote:
> the assumption is that we will never get stuck in this forever. if we
> do then this fix is broken and we need to redesign the exit mechanism.
> (i was debating just calling exit(0) instead of fdetach(), but iirc you
> spent a while coming up with the door thread exit dance, hence and i
> didn't want to change it too much.)
> my assumption is that in this case we want to exit as quickly as
> possible. By doing a yeild, i'm assuming that the doors thread in our
> process should get scheduled before we do and hopefully finish up it's
> work, there by allow us to exit (and not spinning too much).
Thanks for filing the related bug.
Did you catch this in action, with dtrace to know where that EBUSY
is coming from? If we knew what was doing set_errno(EBUSY)...
Daniel Price, Solaris Kernel Engineering http://blogs.sun.com/dp
zones-discuss mailing list