From owner-freebsd-current Mon Jan 22 14:22: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 9411E37B402 for ; Mon, 22 Jan 2001 14:21:52 -0800 (PST) Received: (qmail 95113 invoked by uid 1142); 22 Jan 2001 22:21:51 -0000 Date: 22 Jan 2001 14:21:51 -0800 Date: Mon, 22 Jan 2001 12:42:05 -0800 From: Jason Evans To: Mike Smith Cc: current@freebsd.org Subject: Re: current panics in mount(2) Message-ID: <20010122124205.D69199@canonware.com> References: <200101222016.f0MKGc001040@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101222016.f0MKGc001040@mass.dis.org>; from msmith@freebsd.org on Mon, Jan 22, 2001 at 12:16:38PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 22, 2001 at 12:16:38PM -0800, Mike Smith wrote: > In the meantime, perhaps we could > ask that one of the SMPng rules of engagement mandate that no mutex > structures or structure members should ever be exported as part of a > userspace interface? This sounds fine in principle, but the real problem is that kernel structures are exported. In order for us to fix some of the places where structures are exported and an embedded mutex becomes necessary, we would have to go out of our way to fix an existing design flaw. Under normal circumstances, I would agree with you that broken code should be fixed as it is modified. However, the amount of work that the SMPng project is already taking on is overwhelming. Placing this additional burden on the SMPng developers would in my opinion be detrimental to the medium-term success of the project. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message