To a cursory examination, it looks like it's possible that a number of
syscalls that touch only process state (particularly read-only ones
like getcwd, getpid, etc. but also some that change state, like
chdir, chroot, and a few others) could easily take subsystem locks
instead of the giant lock.

Is this correct?

-- 
 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