From owner-freebsd-arch Fri Mar 29 12:33: 2 2002 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 878B937B405; Fri, 29 Mar 2002 12:32:58 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g2TKWae7079086; Fri, 29 Mar 2002 21:32:36 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Alfred Perlstein Cc: John Baldwin , arch@FreeBSD.ORG Subject: Re: curthread vs. passing thread pointers around In-Reply-To: Your message of "Fri, 29 Mar 2002 12:25:04 PST." <20020329202504.GZ93885@elvis.mu.org> Date: Fri, 29 Mar 2002 21:32:36 +0100 Message-ID: <79085.1017433956@critter.freebsd.dk> From: Poul-Henning Kamp 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 In message <20020329202504.GZ93885@elvis.mu.org>, Alfred Perlstein writes: >* Poul-Henning Kamp [020329 11:55] wrote: >> In message <20020329194158.GX93885@elvis.mu.org>, Alfred Perlstein writes: >> >* John Baldwin [020329 11:32] wrote: >> >> During a discussion on the smp@ list about changes to the suser() >> >> API to make use of td_ucred, [...] >> >> On a related note: I intend to change the open/close/ioctl interface >> to device drivers from a "struct thread *" to a "struct ucred *". > >What about people (ab)?using the device driver interface for proc >related stuff? The main purpose of the excercise is stop such abuse: People think they can track per instance using that argument, and _that_ just ain't going to happen until we hang devices directly under struct file and doing that will screw filesystems which use VOP's to access their device big time. There are two cases of non-abuse which I know off: streams and /dev/fd* streams I'm not sure about yet (is it even in use any more ?) /dev/fd could be solved by embedding fdescfs into devfs. Either way, it's a major patch, which can only partially be machine generated so it is probably not iminent. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message