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:   Thu, 18 Aug 2022 14:14:37 +0100
From:   David Howells <dhowells@...hat.com>
To:     Paul Moore <paul@...l-moore.com>
Cc:     dhowells@...hat.com, Ondrej Mosnacek <omosnace@...hat.com>,
        Al Viro <viro@...iv.linux.org.uk>,
        Trond Myklebust <trond.myklebust@...merspace.com>,
        Anna Schumaker <anna@...nel.org>,
        Scott Mayhew <smayhew@...hat.com>,
        Jeff Layton <jlayton@...nel.org>,
        Casey Schaufler <casey@...aufler-ca.com>,
        linux-nfs <linux-nfs@...r.kernel.org>,
        SElinux list <selinux@...r.kernel.org>,
        Linux Security Module list 
        <linux-security-module@...r.kernel.org>,
        Linux FS Devel <linux-fsdevel@...r.kernel.org>,
        dwysocha@...hat.com,
        Linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] nfs: Fix automount superblock LSM init problem, preventing sb sharing

Paul Moore <paul@...l-moore.com> wrote:

> I guess my question is this: for inodes inside the superblock, does
> their superblock pointer point to the submount's superblock, or the
> parent filesystem's superblock?

They have to point to the submount superblock.  Too many things would break, I
think, if inode->i_sb pointed to the wrong place.  As far as the VFS is
concerned, apart from the way it is mounted, it's a perfectly normal
superblock.

David

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ