From owner-freebsd-hackers Thu Aug 9 11:12:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id C439237B403 for ; Thu, 9 Aug 2001 11:12:33 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id LAA29392; Thu, 9 Aug 2001 11:12:26 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010808222019.92C923A07E@postfix.sekt7.org> Date: Thu, 09 Aug 2001 11:12:28 -0700 (PDT) From: John Baldwin To: Evan Sarmiento Subject: RE: mutex locking pgrp Cc: freebsd-hackers@FreeBSD.org 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 On 08-Aug-01 Evan Sarmiento wrote: > 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? Seigo Tanimura-san is already working on such a patch. tanimura@FreeBSD.org -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message