From owner-freebsd-current Fri Oct 24 04:31:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA10176 for current-outgoing; Fri, 24 Oct 1997 04:31:40 -0700 (PDT) (envelope-from owner-freebsd-current) Received: from salmon.maths.tcd.ie (mmdf@salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id EAA10171; Fri, 24 Oct 1997 04:31:37 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie by salmon.maths.tcd.ie via local-salmon id aa02348; 24 Oct 97 12:31 +0100 To: Terry Lambert cc: KATO Takenori , current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Recursive mount [ was Re: -STABLE reboots ] In-reply-to: Your message of "Thu, 23 Oct 1997 18:22:29 -0000." <199710231822.LAA29050@usr02.primenet.com> Date: Fri, 24 Oct 1997 12:31:28 +0100 From: David Malone Message-ID: <9710241231.aa02348@salmon.maths.tcd.ie> Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Makeing mount priveledged is a kludge. Indeed - though might it be useful for other reasons? (User NFS mounts a directory from their laptop, which they take home, leaving you unable to unmount that directory and all its ancestors? Unless forced umounting of NFS works in 3.0) > Is this a production environment patch? I've a dual processor machine with about 1000 undergrads with accounts on it, so its really a matter of time before someone discovers how to knock it over that way. > There's not really any > conceptual difference between root and non-root mounts, once the > greation of a mount struct instance is abstracted from it's mapping > into the FS hierarchy by moving the latter into common code. I take it that this would factor the recursive lock problem out of the VFS code into the generic mount code, and make it a bit more straight forward to fix? David.