linux-kernel - Re: [RFC][PATCH 0/9] VFS: Introduce mount context

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]

Date:   Wed, 03 May 2017 13:27:19 -0400
From:   Jeff Layton <jlayton@...chiereds.net>
To:     David Howells <dhowells@...hat.com>
Cc:     viro@...iv.linux.org.uk, linux-fsdevel@...r.kernel.org,
        linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org,
        mszeredi@...hat.com
Subject: Re: [RFC][PATCH 0/9] VFS: Introduce mount context

On Wed, 2017-05-03 at 17:50 +0100, David Howells wrote:
> Jeff Layton <jlayton@...chiereds.net> wrote:
> 
> > >  (*) Move the walk-from-root stuff that nfs has to generic code so that you
> > >      can do something akin to:
> > > 
> > > 	mount /dev/sda1:/foo/bar /mnt
> > > 
> > >      See nfs_follow_remote_path() and mount_subtree().  This is slightly
> > >      tricky in NFS as we have to prevent referral loops.
> > > 
> > 
> > ':' is a legitimate character in a path component. How will you
> > distinguish that case?
> 
> Fair point.  Could instead do something like:
> 
> 	mount /dev/sda1 /mnt -o subroot=/foo/bar
> 
> or just limit it to the fsopen interface.
> 
> 

Yeah, something like that would certainly work. I like the basic idea
though of combining a mount and bind mount for local fs'.
-- 
Jeff Layton <jlayton@...chiereds.net>