Date: Tue, 10 Sep 2002 20:28:47 -0700 (PDT) From: Don Lewis <dl-freebsd@catspoiler.org> To: nate@root.org Cc: current@FreeBSD.ORG Subject: Re: Locking problems in exec Message-ID: <200209110328.g8B3Slwr096727@gw.catspoiler.org> In-Reply-To: <Pine.BSF.4.21.0209102018080.19925-100000@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200209110328.g8B3Slwr096727>