From owner-p4-projects Wed May 15 11:39:26 2002 Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 0856137B407; Wed, 15 May 2002 11:39:05 -0700 (PDT) Delivered-To: perforce@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3739737B406 for ; Wed, 15 May 2002 11:39:00 -0700 (PDT) Received: (from perforce@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g4FId0n83607 for perforce@freebsd.org; Wed, 15 May 2002 11:39:00 -0700 (PDT) (envelope-from bb+lists.freebsd.perforce@cyrus.watson.org) Date: Wed, 15 May 2002 11:39:00 -0700 (PDT) Message-Id: <200205151839.g4FId0n83607@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: perforce set sender to bb+lists.freebsd.perforce@cyrus.watson.org using -f From: Robert Watson Subject: PERFORCE change 11368 for review To: Perforce Change Reviews Sender: owner-p4-projects@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG http://people.freebsd.org/~peter/p4db/chv.cgi?CH=11368 Change 11368 by rwatson@rwatson_tislabs on 2002/05/15 11:38:43 Integ merge-o. Kept a proc lock release where I shouldn't have in the setuid/domain transition case. Remove the proc_lock so that the later debugging lock assertion doesn't cause a panic. Affected files ... ... //depot/projects/trustedbsd/mac/sys/kern/kern_exec.c#19 edit Differences ... ==== //depot/projects/trustedbsd/mac/sys/kern/kern_exec.c#19 (text+ko) ==== @@ -385,7 +385,6 @@ if (credential_changing && ((imgp->vp->v_mount->mnt_flag & MNT_NOSUID) == 0) && ((p->p_flag & P_TRACED) == 0)) { - PROC_UNLOCK(p); /* * Turn off syscall tracing for set-id programs, except for * root. Record any set-id flags first to make sure that To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe p4-projects" in the body of the message