Re: kern/50430 (syscall_disestablish() can remove active syscalls)

[pgoyette%NetBSD.org@localhost]

Synopsis: syscall_disestablish() can remove active syscalls

State-Changed-From-To: open->closed
State-Changed-By: pgoyette%NetBSD.org@localhost
State-Changed-When: Wed, 18 Nov 2015 23:00:21 +0000
State-Changed-Why:
Based on further investigation, this PR seems not to be a problem
after all!

With a fairly simple test program, and a few extra printf()s in
strategic locations, I've determined that we never have "nested"
active syscalls.  If a signal gets delivered to the process, any
currently-active syscall is terminated, with status of either
EINTR or ERESTART.  In the ERESTART case, the syscall will be
automatically restarted.  (I'm still trying to find the code that
implements these empirical results.)