summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorcsjp <csjp@FreeBSD.org>2006-04-10 14:07:28 +0000
committercsjp <csjp@FreeBSD.org>2006-04-10 14:07:28 +0000
commit8ddf669db32094a2aaef50ab626814da6281396f (patch)
treea258c40e04a866e14d2fc6a29bbc0c8e980a45c6
parent551b3c3b208ec5c85da75b673e2e003441cba776 (diff)
downloadFreeBSD-src-8ddf669db32094a2aaef50ab626814da6281396f.zip
FreeBSD-src-8ddf669db32094a2aaef50ab626814da6281396f.tar.gz
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
-rw-r--r--sys/kern/kern_exit.c2
1 files changed, 0 insertions, 2 deletions
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
OpenPOWER on IntegriCloud