linux-kernel - Re: nfs4 filesystem mounted via the "bind" option reports wrong fstype

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070827193242.GJ3118@fieldses.org>
Date:	Mon, 27 Aug 2007 15:32:42 -0400
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	Al Viro <viro@....linux.org.uk>
Cc:	Gabriel Barazer <gabriel@...va.fr>, nfsv4@...ux-nfs.org,
	nfs@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
	jkar8572@...rs.sourceforge.net
Subject: Re: nfs4 filesystem mounted via the "bind" option reports wrong
	fstype

On Mon, Aug 27, 2007 at 08:15:07PM +0100, Al Viro wrote:
> On Mon, Aug 27, 2007 at 02:40:59PM -0400, J. Bruce Fields wrote:
>  
> > There's no reason not to just mount server:/exports/data directly at
> > /home/data; the bind mounts are just a workaround for the somewhat
> > primitive exports facility on the server side.
> 
> Bullshit.  Bindings are first-class operations on _client_, regardless
> of fs types involved.

I know.  Did I say something to the contrary?

Maybe I was too terse; in more detail: the original poster appears to be
mounting server:/exports/data by first mounting server:/ somewhere and
then bind-mounting the exports/data someplace else.  I couldn't see an
obvious reason they'd be using two steps instead of just performing a
single mount of server:/exports/data.

So my assumption was that this was due to a confused memory of some
server-side setup instructions.  (On the server side, nfs4 export setup
often requires the administrator to do some extra bind mounts which
shouldn't really be necessary.)

--b.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/