From: Jeff Layton <jlayton@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-cifs <linux-cifs@vger.kernel.org>,
ceph-devel <ceph-devel@vger.kernel.org>,
linux-nfs <linux-nfs@vger.kernel.org>,
Chuck Lever <chuck.lever@oracle.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [GIT PULL] file locking changes for v6.2-rc1
Date: Tue, 06 Dec 2022 08:11:43 -0500 [thread overview]
Message-ID: <d3ba2c7f26958242c0a31b8f966e7c3d251a9e0f.camel@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2376 bytes --]
The following changes since commit 094226ad94f471a9f19e8f8e7140a09c2625abaa:
Linux 6.1-rc5 (2022-11-13 13:12:55 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git tags/locks-v6.2
for you to fetch changes up to f2f2494c8aa3cc317572c4674ef256005ebc092b:
Add process name and pid to locks warning (2022-11-30 05:08:10 -0500)
----------------------------------------------------------------
The main change here is to add the new locks_inode_context helper, and
convert all of the places that dereference inode->i_flctx directly to
use that instead.
There a new helper to indicate whether any locks are held on an inode.
This is mostly for Ceph but may be usable elsewhere too.
Andi Kleen requested that we print the PID when the LOCK_MAND warning
fires, to help track down applications trying to use it.
Finally, we added some new warnings to some of the file locking
functions that fire when the ->fl_file and filp arguments differ. This
helped us find some long-standing bugs in lockd. Patches for those are
in Chuck Lever's tree and should be in his v6.2 PR. After that patch,
people using NFSv2/v3 locking may see some warnings fire until those go
in.
Happy Holidays!
----------------------------------------------------------------
Andi Kleen (1):
Add process name and pid to locks warning
Jeff Layton (9):
filelock: WARN_ON_ONCE when ->fl_file and filp don't match
filelock: new helper: vfs_inode_has_locks
filelock: add a new locks_inode_context accessor function
ceph: use locks_inode_context helper
cifs: use locks_inode_context helper
ksmbd: use locks_inode_context helper
lockd: use locks_inode_context helper
nfs: use locks_inode_context helper
nfsd: use locks_inode_context helper
fs/ceph/locks.c | 4 ++--
fs/cifs/file.c | 2 +-
fs/ksmbd/vfs.c | 2 +-
fs/lockd/svcsubs.c | 4 ++--
fs/locks.c | 50 ++++++++++++++++++++++++++++++++++++++------------
fs/nfs/delegation.c | 2 +-
fs/nfs/nfs4state.c | 2 +-
fs/nfs/pagelist.c | 2 +-
fs/nfs/write.c | 4 ++--
fs/nfsd/nfs4state.c | 6 +++---
include/linux/fs.h | 20 ++++++++++++++++++++
11 files changed, 72 insertions(+), 26 deletions(-)
--
Jeff Layton <jlayton@kernel.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 862 bytes --]
next reply other threads:[~2022-12-06 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 13:11 Jeff Layton [this message]
2022-12-12 17:33 ` 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=d3ba2c7f26958242c0a31b8f966e7c3d251a9e0f.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--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
all inboxes | Powered by JetHome®