On 10 Sep, Nate Lawson wrote:

> I'm not sure why fdcheckstd() and setugidsafety() couldn't both happen
> before grabbing the proc lock.  Dropping locks in the middle or
> pre-allocating should always be a last resort.

That is ok as long as there aren't other threads that can mess things up
after fdcheckstd() and setugidsafety() have done their thing.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to