From: Luis Chamberlain <mcgrof@kernel.org>
To: viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, p.raghav@samsung.com,
hch@infradead.org, john.johansen@canonical.com,
dhowells@redhat.com, mcgrof@kernel.org
Subject: [RFC 0/3] fs: kill old ms_* flags for internal sb
Date: Mon, 9 Jan 2023 18:25:51 -0800 [thread overview]
Message-ID: <20230110022554.1186499-1-mcgrof@kernel.org> (raw)
David had started the sb flag split for internal flags through
commit e462ec50cb5 ("VFS: Differentiate mount flags (MS_*) from internal
superblock flags") but it seems we just never axed out the old flag
usage.
I found this while inspecting adding a new temporary flag for the
superblock for filesystem freeze support. This doesn't go even build
tested, hence RFC.
Luis Chamberlain (3):
apparmor: use SB_* flags for private sb flags
fs: use SB_NOUSER on path_mount() instead of deprecated MS_NOUSER
fs: remove old MS_* internal flags for the superblock
fs/namespace.c | 2 +-
include/uapi/linux/mount.h | 8 --------
security/apparmor/include/mount.h | 3 ++-
security/apparmor/lsm.c | 1 +
security/apparmor/mount.c | 2 +-
tools/include/uapi/linux/mount.h | 8 --------
6 files changed, 5 insertions(+), 19 deletions(-)
--
2.35.1
next reply other threads:[~2023-01-10 2:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 2:25 Luis Chamberlain [this message]
2023-01-10 2:25 ` [RFC 1/3] apparmor: use SB_* flags for private sb flags Luis Chamberlain
2023-01-10 23:40 ` Al Viro
2023-01-10 2:25 ` [RFC 2/3] fs: use SB_NOUSER on path_mount() instead of deprecated MS_NOUSER Luis Chamberlain
2023-01-10 23:43 ` Al Viro
2023-01-10 2:25 ` [RFC 3/3] fs: remove old MS_* internal flags for the superblock Luis Chamberlain
2023-01-10 23:54 ` Al Viro
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=20230110022554.1186499-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=john.johansen@canonical.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=p.raghav@samsung.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).