[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-id: <176480168199.16766.17148776636684804633@noble.neil.brown.name>
Date: Thu, 04 Dec 2025 09:41:21 +1100
From: NeilBrown <neilb@...mail.net>
To: "Chuck Lever" <cel@...nel.org>
Cc: "Jeff Layton" <jlayton@...nel.org>,
"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>,
"Matthew Wilcox (Oracle)" <willy@...radead.org>,
"Jonathan Corbet" <corbet@....net>, "Olga Kornievskaia" <okorniev@...hat.com>,
"Dai Ngo" <Dai.Ngo@...cle.com>, "Tom Talpey" <tom@...pey.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, linux-nfs@...r.kernel.org
Subject: Re: [PATCH 1/2] filelock: add lease_dispose_list() helper
On Thu, 04 Dec 2025, Chuck Lever wrote:
>
> On Mon, Dec 1, 2025, at 10:08 AM, Jeff Layton wrote:
> > ...and call that from the lease handling code instead of
> > locks_dispose_list(). Remove the lease handling parts from
> > locks_dispose_list().
>
> The actual change here isn't bothering me, but I'm having trouble
> understanding why it's needed. It doesn't appear to be a strict
> functional prerequisite for 2/2.
This was almost exactly my thought too. The commit message should say
*why* the change is being made and this one just left us guessing.
But I *do* like the change and would rather it were kept in the series,
but with a simple addition to the commit message saying that is a
simplification that isn't strictly necessary.
Thanks,
NeilBrown
Powered by blists - more mailing lists