From: David Howells <dhowells@redhat.com>
To: Anna Schumaker <anna@kernel.org>
Cc: dhowells@redhat.com, Al Viro <viro@zeniv.linux.org.uk>,
Jeff Layton <jlayton@kernel.org>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Scott Mayhew <smayhew@redhat.com>,
Paul Moore <paul@paul-moore.com>,
Casey Schaufler <casey@schaufler-ca.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
SElinux list <selinux@vger.kernel.org>,
Linux Security Module list
<linux-security-module@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
David Wysochanski <dwysocha@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] vfs, security: Fix automount superblock LSM init problem, preventing NFS sb sharing
Date: Thu, 08 Sep 2022 21:31:21 +0100 [thread overview]
Message-ID: <3658630.1662669081@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAFX2JfmoovJHUBRy6U=yKJt_pAEF0tLadSK+CFqabPcatXe6EQ@mail.gmail.com>
Anna Schumaker <anna@kernel.org> wrote:
> > + fc->lsm_set = true;
>
> I was wondering if there is any way to have security_sb_set_mnt_opts()
> or security_sb_clone_mnt_opts() set this value automatically? A quick
> "git-grep" for security_sb_set_mnt_opts() shows that it's also called
> by btrfs at some point, so having this done automatically feels less
> fragile to me than requiring individual filesystems to set it
> manually.
Hmmm... I wonder if cifs and afs should be calling
security_sb_clone_mnt_opts() also.
David
prev parent reply other threads:[~2022-09-08 20:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 10:09 [PATCH v4] vfs, security: Fix automount superblock LSM init problem, preventing NFS sb sharing David Howells
2022-08-26 8:24 ` Christian Brauner
2022-08-26 17:11 ` Casey Schaufler
2022-08-30 8:49 ` David Howells
2022-08-30 13:47 ` Casey Schaufler
2022-08-31 13:48 ` David Howells
2022-08-31 16:52 ` Casey Schaufler
2022-09-01 5:04 ` Al Viro
2022-09-01 11:47 ` David Howells
2022-09-08 19:35 ` Anna Schumaker
2022-09-08 20:31 ` David Howells [this message]
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=3658630.1662669081@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=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).