From 8ddf669db32094a2aaef50ab626814da6281396f Mon Sep 17 00:00:00 2001 From: csjp Date: Mon, 10 Apr 2006 14:07:28 +0000 Subject: Kill the last Giant acquisition in the exit(2) code. This Giant acquisition doesn't appear to be protecting anything. Most of consumers funsetownlst(9) do not appear to be picking up Giant anywhere. This was originally a part of my Giant exit(2) clean up revision 1.272 but I thought it was a good idea to leave it out until we were able to analyze it better. Tested by: kris MFC after: 3 weeks --- sys/kern/kern_exit.c | 2 -- 1 file changed, 2 deletions(-) (limited to 'sys/kern/kern_exit.c') diff --git a/sys/kern/kern_exit.c b/sys/kern/kern_exit.c index 86e6fc3..bd44b48 100644 --- a/sys/kern/kern_exit.c +++ b/sys/kern/kern_exit.c @@ -266,9 +266,7 @@ retry: * Reset any sigio structures pointing to us as a result of * F_SETOWN with our pid. */ - mtx_lock(&Giant); /* XXX: not sure if needed */ funsetownlst(&p->p_sigiolst); - mtx_unlock(&Giant); /* * If this process has an nlminfo data area (for lockd), release it -- cgit v1.1