From owner-freebsd-arch Fri Mar 29 15:52:54 2002 Delivered-To: freebsd-arch@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id B079437B405; Fri, 29 Mar 2002 15:52:50 -0800 (PST) Received: from pool0156.cvx40-bradley.dialup.earthlink.net ([216.244.42.156] helo=mindspring.com) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16r6Ar-0000hw-00; Fri, 29 Mar 2002 15:52:49 -0800 Message-ID: <3CA4FE3B.C5EE8F4A@mindspring.com> Date: Fri, 29 Mar 2002 15:52:27 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: John Baldwin , arch@FreeBSD.org Subject: Re: curthread vs. passing thread pointers around References: <20020329194158.GX93885@elvis.mu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > For instance, some APIs are broken such that they allow the passing > of a proc/thread in, but if it isn't curproc then we die a painful > death. Those functions need to stop taking a proc/thread pointer > and be documented that they use the current process for cred/misc > processing. Heh. My reaction was that they should be fixed to not die a painful death because of an implied equality dependency that shouldn't be there in the first place... not have the passed value ripped out so that the assumption can be enshrined for all time. Tomato/tomato. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message