From: David Howells <dhowells@redhat.com>
To: Paul Moore <paul@paul-moore.com>
Cc: dhowells@redhat.com, Ondrej Mosnacek <omosnace@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna@kernel.org>,
Scott Mayhew <smayhew@redhat.com>,
Jeff Layton <jlayton@kernel.org>,
Casey Schaufler <casey@schaufler-ca.com>,
linux-nfs <linux-nfs@vger.kernel.org>,
SElinux list <selinux@vger.kernel.org>,
Linux Security Module list
<linux-security-module@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
dwysocha@redhat.com,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] nfs: Fix automount superblock LSM init problem, preventing sb sharing
Date: Thu, 18 Aug 2022 14:14:37 +0100 [thread overview]
Message-ID: <2026286.1660828477@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAHC9VhTpqvFbjKG5FMKGRBRHavOUrsCSFgayh+BNgSrry8bWLg@mail.gmail.com>
Paul Moore <paul@paul-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
next prev parent reply other threads:[~2022-08-18 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 13:36 [PATCH v3] nfs: Fix automount superblock LSM init problem, preventing sb sharing David Howells
2022-08-08 17:04 ` Jeff Layton
2022-08-11 12:28 ` Ondrej Mosnacek
2022-08-16 3:25 ` Paul Moore
2022-08-18 13:14 ` David Howells [this message]
2022-08-19 2:07 ` Paul Moore
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026286.1660828477@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=anna@kernel.org \
--cc=casey@schaufler-ca.com \
--cc=dwysocha@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=smayhew@redhat.com \
--cc=trond.myklebust@hammerspace.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).