Date: Fri, 29 Mar 2002 15:52:27 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Alfred Perlstein <bright@mu.org> Cc: John Baldwin <jhb@FreeBSD.org>, arch@FreeBSD.org Subject: Re: curthread vs. passing thread pointers around Message-ID: <3CA4FE3B.C5EE8F4A@mindspring.com> References: <XFMail.20020329143222.jhb@FreeBSD.org> <20020329194158.GX93885@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3CA4FE3B.C5EE8F4A>