From owner-p4-projects@FreeBSD.ORG Mon Jan 29 20:33:32 2007 Return-Path: X-Original-To: p4-projects@freebsd.org Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id E23B716A405; Mon, 29 Jan 2007 20:33:31 +0000 (UTC) X-Original-To: perforce@FreeBSD.org Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 97D4816A401 for ; Mon, 29 Jan 2007 20:33:31 +0000 (UTC) (envelope-from rdivacky@FreeBSD.org) Received: from repoman.freebsd.org (repoman.freebsd.org [69.147.83.41]) by mx1.freebsd.org (Postfix) with ESMTP id 88B3313C49D for ; Mon, 29 Jan 2007 20:33:31 +0000 (UTC) (envelope-from rdivacky@FreeBSD.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.13.6/8.13.6) with ESMTP id l0TKXVIs009640 for ; Mon, 29 Jan 2007 20:33:31 GMT (envelope-from rdivacky@FreeBSD.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.13.6/8.13.4/Submit) id l0TKXV0g009634 for perforce@freebsd.org; Mon, 29 Jan 2007 20:33:31 GMT (envelope-from rdivacky@FreeBSD.org) Date: Mon, 29 Jan 2007 20:33:31 GMT Message-Id: <200701292033.l0TKXV0g009634@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to rdivacky@FreeBSD.org using -f From: Roman Divacky To: Perforce Change Reviews Cc: Subject: PERFORCE change 113673 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2007 20:33:32 -0000 http://perforce.freebsd.org/chv.cgi?CH=113673 Change 113673 by rdivacky@rdivacky_witten on 2007/01/29 20:33:26 o dont set p->p_emuldata to NULL when the process is exiting. it doesnt make any sense and only costs us 2 mtx operations. o dont lock emul_data to unlock it on the very next line. it doesnt serve any purpose and only slow things down. There might be race though, I am not sure and this needs some checking. Add a comment about it. Affected files ... .. //depot/projects/linuxolator/src/sys/compat/linux/linux_emul.c#27 edit Differences ... ==== //depot/projects/linuxolator/src/sys/compat/linux/linux_emul.c#27 (text+ko) ==== @@ -167,10 +167,6 @@ EMUL_SHARED_WLOCK(&emul_shared_lock); LIST_REMOVE(em, threads); - PROC_LOCK(p); - p->p_emuldata = NULL; - PROC_UNLOCK(p); - em->shared->refs--; if (em->shared->refs == 0) free(em->shared, M_LINUX); @@ -241,12 +237,15 @@ && p->p_sysent == &elf_linux_sysvec)) { struct linux_emuldata *em; - em = em_find(p, EMUL_DOLOCK); + /* + * XXX: is it racy? if p->p_sysent still points at linux_sysvec + * it is. someone please check this. we were running with + * this race for quite a long time though. + */ + em = em_find(p, EMUL_DONTLOCK); KASSERT(em != NULL, ("proc_exec: emuldata not found.\n")); - EMUL_UNLOCK(&emul_lock); - EMUL_SHARED_WLOCK(&emul_shared_lock); LIST_REMOVE(em, threads);