From: Jeff Layton <jlayton@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>,
Bruce Fields <bfields@fieldses.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: [GIT PULL] File locking changes for v5.15
Date: Fri, 27 Aug 2021 08:49:36 -0400 [thread overview]
Message-ID: <03b3f42bbc92fdd1c798c29451eac66a0576adf1.camel@kernel.org> (raw)
The following changes since commit 9ff50bf2f2ff5fab01cac26d8eed21a89308e6ef:
Merge tag 'clk-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux (2021-08-21 11:27:16 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git locks-v5.15
for you to fetch changes up to 2949e8427af3bb74a1e26354cb68c1700663c827:
fs: clean up after mandatory file locking support removal (2021-08-24 07:52:45 -0400)
----------------------------------------------------------------
Hi Linus,
Sending this along early as I don't expect it to change between now and
when the merge window opens.
This PR starts with a couple of fixes for potential deadlocks in the
fowner/fasync handling. The next patch removes the old mandatory locking
code from the kernel altogether. The last patch cleans up rw_verify_area
a bit more after the mandatory locking removal.
Thanks!
----------------------------------------------------------------
Desmond Cheong Zhi Xi (2):
fcntl: fix potential deadlocks for &fown_struct.lock
fcntl: fix potential deadlock for &fasync_struct.fa_lock
Jeff Layton (1):
fs: remove mandatory file locking support
Lukas Bulwahn (1):
fs: clean up after mandatory file locking support removal
Documentation/filesystems/mandatory-locking.rst | 188 --------------------------------------------
fs/9p/vfs_file.c | 13 ---
fs/Kconfig | 10 ---
fs/afs/flock.c | 4 -
fs/ceph/locks.c | 3 -
fs/fcntl.c | 18 +++--
fs/gfs2/file.c | 3 -
fs/locks.c | 117 +--------------------------
fs/namei.c | 4 +-
fs/namespace.c | 29 +++----
fs/nfs/file.c | 4 -
fs/nfsd/nfs4state.c | 14 ----
fs/nfsd/vfs.c | 23 +-----
fs/ocfs2/locks.c | 4 -
fs/open.c | 8 +-
fs/read_write.c | 17 +---
fs/remap_range.c | 12 ---
include/linux/fs.h | 84 --------------------
mm/mmap.c | 6 --
mm/nommu.c | 3 -
20 files changed, 28 insertions(+), 536 deletions(-)
delete mode 100644 Documentation/filesystems/mandatory-locking.rst
--
Jeff Layton <jlayton@kernel.org>
next reply other threads:[~2021-08-27 12:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 12:49 Jeff Layton [this message]
2021-08-30 19:46 ` [GIT PULL] File locking changes for v5.15 pr-tracker-bot
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=03b3f42bbc92fdd1c798c29451eac66a0576adf1.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=bfields@fieldses.org \
--cc=desmondcheongzx@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=torvalds@linux-foundation.org \
--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).