From: Dai Ngo <dai.ngo@oracle.com>
To: Jeff Layton <jlayton@kernel.org>,
chuck.lever@oracle.com, neilb@ownmail.net, okorniev@redhat.com,
tom@talpey.com, hch@lst.de, alex.aring@gmail.com,
viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz
Cc: linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH v4 1/3] locks: Introduce lm_breaker_timedout operation to lease_manager_operations
Date: Wed, 19 Nov 2025 08:32:27 -0800 [thread overview]
Message-ID: <ec0f990d-616d-4284-944f-68929fc671a1@oracle.com> (raw)
In-Reply-To: <dffee3dcbea10e88666bd145bf5f66bb921231dd.camel@kernel.org>
On 11/19/25 5:52 AM, Jeff Layton wrote:
> On Mon, 2025-11-17 at 11:41 -0800, Dai Ngo wrote:
>> On 11/17/25 10:02 AM, Jeff Layton wrote:
>>> On Sat, 2025-11-15 at 11:16 -0800, Dai Ngo wrote:
>>>> Some consumers of the lease_manager_operations structure need
>>>> to perform additional actions when a lease break, triggered by
>>>> a conflict, times out.
>>>>
>>>> The NFS server is the first consumer of this operation.
>>>>
>>>> When a pNFS layout conflict occurs and the lease break times
>>>> out — resulting in the layout being revoked and its file lease
>>>> removed from the flc_lease list — the NFS server must issue a
>>>> fence operation. This operation ensures that the client is
>>>> prevented from accessing the data server after the layout
>>>> revocation.
>>>>
>>>> Fixes: f99d4fbdae67 ("nfsd: add SCSI layout support")
>>>> Signed-off-by: Dai Ngo <dai.ngo@oracle.com>
>>>> ---
>>>> Documentation/filesystems/locking.rst | 2 ++
>>>> fs/locks.c | 14 +++++++++++---
>>>> include/linux/filelock.h | 2 ++
>>>> 3 files changed, 15 insertions(+), 3 deletions(-)
>>>>
>>>> diff --git a/Documentation/filesystems/locking.rst b/Documentation/filesystems/locking.rst
>>>> index 77704fde9845..cd600db6c4b9 100644
>>>> --- a/Documentation/filesystems/locking.rst
>>>> +++ b/Documentation/filesystems/locking.rst
>>>> @@ -403,6 +403,7 @@ prototypes::
>>>> bool (*lm_breaker_owns_lease)(struct file_lock *);
>>>> bool (*lm_lock_expirable)(struct file_lock *);
>>>> void (*lm_expire_lock)(void);
>>>> + void (*lm_breaker_timedout)(struct file_lease *);
>>>>
>>>> locking rules:
>>>>
>>>> @@ -416,6 +417,7 @@ lm_change yes no no
>>>> lm_breaker_owns_lease: yes no no
>>>> lm_lock_expirable yes no no
>>>> lm_expire_lock no no yes
>>>> +lm_breaker_timedout no no yes
>>>> ====================== ============= ================= =========
>>>>
>>>> buffer_head
>>>> diff --git a/fs/locks.c b/fs/locks.c
>>>> index 04a3f0e20724..1f254e0cd398 100644
>>>> --- a/fs/locks.c
>>>> +++ b/fs/locks.c
>>>> @@ -369,9 +369,15 @@ locks_dispose_list(struct list_head *dispose)
>>>> while (!list_empty(dispose)) {
>>>> flc = list_first_entry(dispose, struct file_lock_core, flc_list);
>>>> list_del_init(&flc->flc_list);
>>>> - if (flc->flc_flags & (FL_LEASE|FL_DELEG|FL_LAYOUT))
>>>> + if (flc->flc_flags & (FL_LEASE|FL_DELEG|FL_LAYOUT)) {
>>>> + if (flc->flc_flags & FL_BREAKER_TIMEDOUT) {
>>>> + struct file_lease *fl = file_lease(flc);
>>>> +
>>>> + if (fl->fl_lmops->lm_breaker_timedout)
>>>> + fl->fl_lmops->lm_breaker_timedout(fl);
>>>> + }
>>> locks_dispose_list() is a common function for locks and leases, and
>>> this is only going to be relevant from __break_lease().
>>>
>>> Can you move this handling into a separate function that is called
>>> before the relevant locks_dispose_list() call in __break_lease()?
>> will fix in v5.
>>
>> -Dai
>>
> That may not work actually, since we may end up with a timed out lease
> on a dispose list in a different codepath.
>
> I just sent this patch:
>
> https://lore.kernel.org/linux-nfs/20251119-dir-deleg-ro-v8-2-81b6cf5485c6@kernel.org/T/#u
>
> Assuming that goes in, then I think calling ->lm_breaker_timedout()
> from lease_dispose_list() should be OK.
Thanks Jeff, I will wait for your patch to go in then rework on this patch.
-Dai
>
>>>> locks_free_lease(file_lease(flc));
>>>> - else
>>>> + } else
>>>> locks_free_lock(file_lock(flc));
>>>> }
>>>> }
>>>> @@ -1482,8 +1488,10 @@ static void time_out_leases(struct inode *inode, struct list_head *dispose)
>>>> trace_time_out_leases(inode, fl);
>>>> if (past_time(fl->fl_downgrade_time))
>>>> lease_modify(fl, F_RDLCK, dispose);
>>>> - if (past_time(fl->fl_break_time))
>>>> + if (past_time(fl->fl_break_time)) {
>>>> lease_modify(fl, F_UNLCK, dispose);
>>>> + fl->c.flc_flags |= FL_BREAKER_TIMEDOUT;
>>>> + }
>>>> }
>>>> }
>>>>
>>>> diff --git a/include/linux/filelock.h b/include/linux/filelock.h
>>>> index c2ce8ba05d06..06ccd6b66012 100644
>>>> --- a/include/linux/filelock.h
>>>> +++ b/include/linux/filelock.h
>>>> @@ -17,6 +17,7 @@
>>>> #define FL_OFDLCK 1024 /* lock is "owned" by struct file */
>>>> #define FL_LAYOUT 2048 /* outstanding pNFS layout */
>>>> #define FL_RECLAIM 4096 /* reclaiming from a reboot server */
>>>> +#define FL_BREAKER_TIMEDOUT 8192 /* lease breaker timed out */
>>>>
>>>> #define FL_CLOSE_POSIX (FL_POSIX | FL_CLOSE)
>>>>
>>>> @@ -49,6 +50,7 @@ struct lease_manager_operations {
>>>> int (*lm_change)(struct file_lease *, int, struct list_head *);
>>>> void (*lm_setup)(struct file_lease *, void **);
>>>> bool (*lm_breaker_owns_lease)(struct file_lease *);
>>>> + void (*lm_breaker_timedout)(struct file_lease *fl);
>>>> };
>>>>
>>>> struct lock_manager {
next prev parent reply other threads:[~2025-11-19 16:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-15 19:16 [Patch v4 0/3] NFSD: Fix server hang when there are multiple layout conflicts Dai Ngo
2025-11-15 19:16 ` [PATCH v4 1/3] locks: Introduce lm_breaker_timedout operation to lease_manager_operations Dai Ngo
2025-11-17 15:39 ` Chuck Lever
2025-11-17 19:17 ` Dai Ngo
2025-11-17 18:02 ` Jeff Layton
2025-11-17 19:41 ` Dai Ngo
2025-11-19 13:52 ` Jeff Layton
2025-11-19 16:32 ` Dai Ngo [this message]
2025-11-19 9:54 ` Christoph Hellwig
2025-11-19 14:04 ` Chuck Lever
2025-11-15 19:16 ` [PATCH v4 2/3] locks: Threads with layout conflict must wait until client was fenced Dai Ngo
2025-11-17 15:47 ` Chuck Lever
2025-11-17 19:21 ` Dai Ngo
2025-11-17 18:21 ` Jeff Layton
2025-11-17 19:49 ` Dai Ngo
2025-11-19 9:53 ` Christoph Hellwig
2025-11-15 19:16 ` [PATCH v4 3/3] FSD: Fix NFS server hang when there are multiple layout conflicts Dai Ngo
2025-11-15 19:44 ` Chuck Lever
2025-11-15 20:20 ` Dai Ngo
2025-11-19 9:56 ` Christoph Hellwig
2025-11-19 16:35 ` Dai Ngo
2025-11-17 15:55 ` Chuck Lever
2025-11-17 19:40 ` Dai Ngo
2025-11-17 21:13 ` Benjamin Coddington
2025-11-17 22:00 ` Dai Ngo
2025-11-19 10:08 ` Christoph Hellwig
2025-11-19 16:52 ` Dai Ngo
2025-11-20 6:50 ` Christoph Hellwig
2025-11-19 10:05 ` Christoph Hellwig
2025-11-19 14:04 ` Benjamin Coddington
2025-11-19 14:09 ` Chuck Lever
2025-11-19 14:12 ` Jeff Layton
2025-11-19 17:06 ` Dai Ngo
2025-11-20 6:52 ` Christoph Hellwig
2025-11-20 6:59 ` Christoph Hellwig
2025-11-19 9:57 ` Christoph Hellwig
2025-11-19 10:08 ` Christoph Hellwig
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=ec0f990d-616d-4284-944f-68929fc671a1@oracle.com \
--to=dai.ngo@oracle.com \
--cc=alex.aring@gmail.com \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@ownmail.net \
--cc=okorniev@redhat.com \
--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).