On Tue, Jun 07, 2005 at 06:43:56PM +0100, David Laight wrote:
> On Tue, Jun 07, 2005 at 10:38:20AM -0700, Matt Thomas wrote:
> > >
> > >Yes. The MD syscall code checks for the SYSCALL_MPSAFE flag and
> > >doesn't take the big-lock if it's set. It's currently only set for
> > >getpid(). Exactly what else it could be easily applied to is less
> > >clear; getpid() is the only true no-brainer that requires taking no
> > >locks on anything at all.
> > 
> > get*gid?
> > get*uid?
> 
> While another thread is doing set*[gu]id ?

It seems to me that if we are using the kernel lock to protect against
_that_, we are misusing it.

-- 
 Thor Lancelot Simon	                                      tls@rek.tjls.com

"The inconsistency is startling, though admittedly, if consistency is to be
 abandoned or transcended, there is no problem."		- Noam Chomsky