From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: linux-nfs@vger.kernel.org, david@redhat.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
w@1wt.eu, cluster-devel@redhat.com, linux-mm@kvack.org,
rostedt@goodmis.org, ebiederm@xmission.com, luto@kernel.org,
linux-fsdevel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net,
torvalds@linux-foundation.org, linux-afs@lists.infradead.org,
ocfs2-devel@oss.oracle.com, viro@zeniv.linux.org.uk
Subject: Re: [Ocfs2-devel] [PATCH v2 0/2] fs: remove support for mandatory locking
Date: Fri, 20 Aug 2021 10:09:03 -0400 [thread overview]
Message-ID: <20210820140903.GA18096@fieldses.org> (raw)
In-Reply-To: <20210820135707.171001-1-jlayton@kernel.org>
On Fri, Aug 20, 2021 at 09:57:05AM -0400, Jeff Layton wrote:
> The first patch in this series adds a new warning that should pop on
> kernels 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?
Sounds good to me.--b.
>
> 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 | 31 +--
> 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, 20 insertions(+), 505 deletions(-)
> delete mode 100644 Documentation/filesystems/mandatory-locking.rst
>
> --
> 2.31.1
_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel
prev parent reply other threads:[~2021-09-13 14:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 13:57 [Ocfs2-devel] [PATCH v2 0/2] fs: remove support for mandatory locking Jeff Layton
2021-08-20 13:57 ` [Ocfs2-devel] [PATCH v2 1/2] fs: warn about impending deprecation of mandatory locks Jeff Layton
2021-08-20 15:49 ` David Laight
2021-08-20 15:50 ` Jeff Layton
2021-08-20 15:52 ` David Hildenbrand
2021-08-20 16:06 ` Jeff Layton
2021-08-20 16:08 ` Steven Rostedt
2021-08-20 13:57 ` [Ocfs2-devel] [PATCH v2 2/2] fs: remove mandatory file locking support Jeff Layton
2021-08-20 14:09 ` J. Bruce Fields [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=20210820140903.GA18096@fieldses.org \
--to=bfields@fieldses.org \
--cc=cluster-devel@redhat.com \
--cc=david@redhat.com \
--cc=ebiederm@xmission.com \
--cc=jlayton@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=luto@kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=viro@zeniv.linux.org.uk \
--cc=w@1wt.eu \
/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).