[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <F3D97B2E-1693-4E31-BBF8-63F7F550ADCB@redhat.com>
Date: Mon, 02 Jun 2025 09:09:01 -0400
From: Benjamin Coddington <bcodding@...hat.com>
To: Jeff Layton <jlayton@...nel.org>
Cc: Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>,
Chuck Lever <chuck.lever@...cle.com>, Alexander Aring <alex.aring@...il.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] filelock: add new locks_wake_up_waiter() helper
On 2 Jun 2025, at 7:58, Jeff Layton wrote:
> Currently the function that does this takes a struct file_lock, but
> __locks_wake_up_blocks() deals with both locks and leases. Currently
> this works because both file_lock and file_lease have the file_lock_core
> at the beginning of the struct, but it's fragile to rely on that.
>
> Add a new locks_wake_up_waiter() function and call that from
> __locks_wake_up_blocks().
>
> Signed-off-by: Jeff Layton <jlayton@...nel.org>
Looks good,
Reviewed-by: Benjamin Coddington <bcodding@...hat.com>
Ben
Powered by blists - more mailing lists