Revert the previous revision for two reasons:

- I can't seem to reproduce the warning I got from WITNESS anymore.
- The fix was wrong.  Since a uidinfo struct is a member of proc, it
  makes sense for the locking order to be such that you are allowed to
  hold proc and then grab the uidinfo lock.

1 files changed, 0 insertions, 2 deletions

diff --git a/sys/kern/kern_exit.c b/sys/kern/kern_exit.c
index 24a4753..71e6288 100644
--- a/sys/kern/kern_exit.c
+++ b/sys/kern/kern_exit.c
@@ -521,10 +521,8 @@ loop:
 			 */
 			PROC_LOCK(p);
 			if (--p->p_cred->p_refcnt == 0) {
-				PROC_UNLOCK(p);
 				crfree(p->p_ucred);
 				uifree(p->p_cred->p_uidinfo);
-				PROC_LOCK(p);
 				FREE(p->p_cred, M_SUBPROC);
 				p->p_cred = NULL;
 			}