From owner-freebsd-current Mon Jan 22 10:54:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 19EF337B400 for ; Mon, 22 Jan 2001 10:54:10 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0MIs4R25928; Mon, 22 Jan 2001 10:54:04 -0800 (PST) Date: Mon, 22 Jan 2001 10:54:04 -0800 From: Alfred Perlstein To: Garrett Wollman Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: current panics in mount(2) Message-ID: <20010122105404.F7240@fw.wintelcom.net> References: <200101221827.NAA40361@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101221827.NAA40361@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Mon, Jan 22, 2001 at 01:27:20PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Garrett Wollman [010122 10:27] wrote: > < said: > > > Somehow there were few problems when `struct mtx' was added to > > `struct ucred'. The critical args were probably usually 0. > > It's a bug that mount(2) uses a bare `struct ucred' and not a > well-defined, user-exportable credential structure (like struct > cmsgcred used for SCM_CREDS ancillary data). I looked at fixing this once, but got scared off because of binary compatibility issues. Would 'fixing' mount to use cmsgcred be acceptable? -- -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-current" in the body of the message