From: Jeff Layton <jlayton@kernel.org>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Jeff Layton <jlayton@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>,
Alexander Aring <alex.aring@gmail.com>,
NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nfs@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [PATCH v8 0/3] vfs: expose delegation support to userland
Date: Wed, 19 Nov 2025 08:42:17 -0500 [thread overview]
Message-ID: <20251119-dir-deleg-ro-v8-0-81b6cf5485c6@kernel.org> (raw)
Stephen hit a couple of problems while merging the last patch in the
directory delegation series, and I found some problems while testing
userland delegations (more fstests forthcoming).
Christian, could you drop the last patch in
vfs-6.19.directory.delegations, and pick up these patches? They should
address all of the problems Stephen reported and make userland
delegation support on files work properly. Let me know if you'd rather I
resend a whole new directory delegation series instead.
To: Alexander Viro <viro@zeniv.linux.org.uk>
To: Christian Brauner <brauner@kernel.org>
To: Jan Kara <jack@suse.cz>
To: Chuck Lever <chuck.lever@oracle.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Jeff Layton <jlayton@kernel.org>
Changes in v8:
- split out lease_dispose_list() helper
- add new ->lm_open_conflict() lease_manager_operation
- Link to v7: https://lore.kernel.org/r/20251117-dir-deleg-ro-v7-1-f8bfd13a3791@kernel.org
Changes in v7:
- have fcntl.h include proper headers for stdint.h integers
- move comment above fcntl_getlease() to the proper place
- add a kerneldoc comment over fcntl_getdeleg()
---
Jeff Layton (3):
vfs: expose delegation support to userland
filelock: add lease_dispose_list() helper
filelock: allow lease_managers to dictate what qualifies as a conflict
fs/fcntl.c | 13 +++
fs/locks.c | 199 ++++++++++++++++++++++++++++-----------------
fs/nfsd/nfs4layouts.c | 11 ++-
fs/nfsd/nfs4state.c | 7 ++
include/linux/filelock.h | 13 +++
include/uapi/linux/fcntl.h | 16 ++++
6 files changed, 181 insertions(+), 78 deletions(-)
---
base-commit: 5c4a3c4961067120fbf6d35622c2e839f9ceba12
change-id: 20251117-dir-deleg-ro-2e6247a1a0a9
Best regards,
--
Jeff Layton <jlayton@kernel.org>
next reply other threads:[~2025-11-19 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 13:42 Jeff Layton [this message]
2025-11-19 13:42 ` [PATCH v8 1/3] vfs: expose delegation support to userland Jeff Layton
2025-11-19 13:42 ` [PATCH v8 2/3] filelock: add lease_dispose_list() helper Jeff Layton
2025-11-19 13:42 ` [PATCH v8 3/3] filelock: allow lease_managers to dictate what qualifies as a conflict 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=20251119-dir-deleg-ro-v8-0-81b6cf5485c6@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=alex.aring@gmail.com \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=tom@talpey.com \
--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).