From owner-freebsd-current  Tue Oct 21 19:17:32 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id TAA26768
          for current-outgoing; Tue, 21 Oct 1997 19:17:32 -0700 (PDT)
          (envelope-from owner-freebsd-current)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA26763
          for <current@FreeBSD.ORG>; Tue, 21 Oct 1997 19:17:29 -0700 (PDT)
          (envelope-from bde@zeta.org.au)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id MAA22074; Wed, 22 Oct 1997 12:13:50 +1000
Date: Wed, 22 Oct 1997 12:13:50 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199710220213.MAA22074@godzilla.zeta.org.au>
To: bde@zeta.org.au, karpen@ocean.campus.luth.se
Subject: Re: -STABLE reboots
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>> The problem is more serious in -current, since mount(2) is unprivileged,
>> so even `mount /foo /foo' panics (if the mounter is root or owns /foo).
>
>Er... Isn't that easilly solvable by mount checking for the two arguments
>being the same?

Of course not, or it would have been fixed years ago.  `mkdir foo; ln foo
bar; mount foo bar' also panics.  Checking inodes isn't enough either,
since `mkdir foo foo/foo; mount foo/foo foo' also panics.

Bruce