From: Jeff Layton <jlayton@kernel.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v3 0/2] fs: remove support for mandatory locking
Date: Fri, 20 Aug 2021 12:39:17 -0400 [thread overview]
Message-ID: <20210820163919.435135-1-jlayton@kernel.org> (raw)
v3: slight revision to verbiage, and use pr_warn_once
The first patch in this series adds a new warning that should pop on
kernels that have mandatory locking enabled when someone mounts a
filesystem with -o mand. The second patch removes support for mandatory
locking altogether.
What I think we probably want to do is apply the first to v5.14 before
it ships and allow the new warning to trickle out into stable kernels.
Then we can merge the second patch in v5.15 to go ahead and remove it.
Sound like a plan?
Jeff Layton (2):
fs: warn about impending deprecation of mandatory locks
fs: remove mandatory file locking support
.../filesystems/mandatory-locking.rst | 188 ------------------
fs/9p/vfs_file.c | 12 --
fs/Kconfig | 10 -
fs/afs/flock.c | 4 -
fs/ceph/locks.c | 3 -
fs/gfs2/file.c | 3 -
fs/locks.c | 116 +----------
fs/namei.c | 4 +-
fs/namespace.c | 25 +--
fs/nfs/file.c | 4 -
fs/nfsd/nfs4state.c | 13 --
fs/nfsd/vfs.c | 15 --
fs/ocfs2/locks.c | 4 -
fs/open.c | 8 +-
fs/read_write.c | 7 -
fs/remap_range.c | 10 -
include/linux/fs.h | 84 --------
mm/mmap.c | 6 -
mm/nommu.c | 3 -
19 files changed, 14 insertions(+), 505 deletions(-)
delete mode 100644 Documentation/filesystems/mandatory-locking.rst
--
2.31.1
next reply other threads:[~2021-08-20 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 16:39 Jeff Layton [this message]
2021-08-20 16:39 ` [Cluster-devel] [PATCH v3 1/2] fs: warn about impending deprecation of mandatory locks Jeff Layton
2021-08-20 16:39 ` [Cluster-devel] [PATCH v3 2/2] fs: remove mandatory file locking support Jeff Layton
2021-08-20 19:45 ` Al Viro
2021-08-23 15:12 ` Guenter Roeck
2021-08-20 18:15 ` [Cluster-devel] [PATCH v3 0/2] fs: remove support for mandatory locking Jeff Layton
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=20210820163919.435135-1-jlayton@kernel.org \
--to=jlayton@kernel.org \
/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).