From owner-freebsd-arch Tue Jan 23 0:13:57 2001 Delivered-To: freebsd-arch@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 8CCB237B401; Tue, 23 Jan 2001 00:13:39 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0N8DdX18914; Tue, 23 Jan 2001 00:13:39 -0800 (PST) Date: Tue, 23 Jan 2001 00:13:39 -0800 From: Alfred Perlstein To: "Brian F. Feldman" Cc: arch@FreeBSD.ORG Subject: Re: struct ucred is evil and must be contained Message-ID: <20010123001339.L26076@fw.wintelcom.net> References: <200101230358.f0N3wvW01298@green.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101230358.f0N3wvW01298@green.dyndns.org>; from green@FreeBSD.ORG on Mon, Jan 22, 2001 at 10:58:56PM -0500 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Brian F. Feldman [010122 19:59] wrote: > Okay, maybe the subject is a bit sensationalistic, but the fact remains that > ucred has grown into a monster, in the same manner of struct proc, that > needs to be carefully contained. In this vain, I've created a struct xucred > and replaced uses of ucred outside of the kernel with it where possible. > > This will also happen to fix the bug that if you screw up your interfaces > (change the size of ucred, for example), mountd and nfsd will not panic the > kernel because of it. This is a very good thing! Comments? As long as it doesn't break world, it looks good. :) Thanks for taking the time to do this. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message