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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 10 Aug 2018 16:13:11 +0100
From:   David Howells <>
To:     Andy Lutomirski <>
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 <>,,,,,, "Theodore Y. Ts'o" <>,
        Miklos Szeredi <>
Subject: Re: BUG: Mount ignores mount options

Andy Lutomirski <> wrote:

> > /dev/loop0 /root/loop0-noacl-noquota-nouser_xattr ext4 rw,relatime,nouser_xattr,noacl 0 0
> > /dev/loop0 /root/loop0-acl-quota-user_xattr ext4 rw,relatime,nouser_xattr,noacl 0 0
> To make sure I understand correctly: the problem is that the second mount
> ignored the options because the device was already mounted, right?
> For the new API, I think the only remotely sane approach is to refuse to
> mount or init or whatever you call it an already mounted bdev. If user code
> genuinely needs to bind-mount an existing mount that is known only by its
> bdev, we can add a specific API just for that.

I'm adding some flags to fsopen() to allow userspace to say whether it wants
no sharing, same parameters-only sharing or anything-goes sharing (as now).

I'm also adding a flag whereby userspace can forbid anyone else from sharing a
new superblock it has just set up.


Powered by blists - more mailing lists