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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 10 Aug 2018 16:53:58 +0100
From:   David Howells <>
To:     "Theodore Y. Ts'o" <>
Cc:, "Eric W. Biederman" <>,,
        John Johansen <>,
        Tejun Heo <>,,
        Paul Moore <>,
        Li Zefan <>,,,
        Casey Schaufler <>,,
        Greg Kroah-Hartman <>,
        Eric Biggers <>,,
        Tetsuo Handa <>,
        Johannes Weiner <>,
        Stephen Smalley <>,,,,,, Miklos Szeredi <>
Subject: Re: BUG: Mount ignores mount options

Theodore Y. Ts'o <> wrote:

> Even *with* file system support, there's no way today for the VFS to
> keep track of whether a pathname resolution came through one
> mountpoint or another, so I can't do something like this:

Ummm...  Isn't that encoded in the vfsmount pointer in struct path?

However, the case folding stuff - is that a superblockism of a mountpointism?

> So if the file system has been mounted with one set of mount options,
> and you want to try to mount it with a conflicting set of mount
> options and you don't want it to silently ignore the mount options,
> the *only* thing we can today is to refuse the mount and return an
> error.  

With fsopen() there is the option to have the filesystem and the LSM attempt
to compare the non-key[*] mount options and reject the attempt to share if
they differ in any way.


[*] sget lookup keys, that is.

Powered by blists - more mailing lists