RFC fs: kill old ms_* flags for internal sb
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest3 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | apparmor: use SB_* flags for private sb flagssecurity/ security/ security/ | +4 | 1 reply | |
| 2/3 | fs: use SB_NOUSER on path_mount() instead of deprecated MS_NOUSERfs/ | +1 | 1 reply | |
| 3/3 | fs: remove old MS_* internal flags for the superblockinclude/ tools/ | +0 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC 0/3] fs: kill old ms_* flags for internal sb
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(-)
Signature · 1 line
2.35.1