From owner-freebsd-hackers Wed Aug 8 15:20:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from postfix.sekt7.org (209-6-248-16.c3-0.lex-ubr1.sbo-lex.ma.cable.rcn.com [209.6.248.16]) by hub.freebsd.org (Postfix) with ESMTP id 6446237B41A for ; Wed, 8 Aug 2001 15:20:23 -0700 (PDT) (envelope-from ems@open-root.org) Received: from smtp.sekt7.org (postfix.sekt7.org [169.69.6.38]) by postfix.sekt7.org (Postfix) with SMTP id 92C923A07E for ; Wed, 8 Aug 2001 18:20:19 -0400 (EDT) From: Evan Sarmiento To: freebsd-hackers@freebsd.org Subject: mutex locking pgrp Message-Id: <20010808222019.92C923A07E@postfix.sekt7.org> Date: Wed, 8 Aug 2001 18:20:19 -0400 (EDT) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I was looking through kern_proc.c, and I noticed that unlike pfind, pgfind does not lock the pointer to a structure being returned, further investigating showed that the definition fo the pgrp structure itself, in proc.h, doesn't have a mtx struct defined within it either. My proposal is to create a patch that would create pgrp locking, by adding a mtx to pgrp, and then a MACRO which locks and unlocks that structure, like PROC_LOCK() Would this create any problems? Also, my pr has been sitting in gnats for a while, I think that patch may be beneficial... http://www.freebsd.org/cgi/query-pr.cgi?pr=29423 -- ----------------------------------- Evan Sarmiento | www.open-root.org ems@sekt7.org | www.sekt7.org/~ems/ ----------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message