From: Chuck Lever <chuck.lever@oracle.com>
To: NeilBrown <neil@brown.name>
Cc: linux-nfs@vger.kernel.org,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
Jeff Layton <jlayton@kernel.org>,
Li Lingfeng <lilingfeng3@huawei.com>
Subject: Re: [PATCH RFT v2] nfsd: provide locking for v4_end_grace
Date: Wed, 2 Jul 2025 19:26:02 -0400 [thread overview]
Message-ID: <7de72319-95ce-46b8-8aa5-33fb211aaadc@oracle.com> (raw)
In-Reply-To: <175149132125.565058.15666202434202898775@noble.neil.brown.name>
On 7/2/25 5:22 PM, NeilBrown wrote:
> On Wed, 02 Jul 2025, Chuck Lever wrote:
>> Hi Neil, handful of nits below.
>>
>>>
>>> [[
>>> v2 - disable laundromat_work while _init is running as well as while
>>> _exit is running. Don't depend on ->nfsd_serv, test
>>> ->client_tracking_ops instead.
>>> ]]
>>
>> Do you want the patch change history to appear in the commit log?
>> Asking because that is not usual practice.
>
> Not really. I'll send something new, likely tomorrow morning.
> What do you think is the best way to handle backporting?
The best practice is to have upstream patches that can apply cleanly to
LTS kernels.
- One patch that can be backported for the fix, one or more for
clean-ups that apply only to master;
- Identify pre-requisites that need to be backported first to make
your fix apply cleanly; or
- Handcraft the fix for each LTS kernel
> Should I
> submit the version that doesn't use disable_delayed_work(), then add a
> patch which changes to use that instead of a flag ?
Post an RFC here, let's see what you're thinking.
--
Chuck Lever
next prev parent reply other threads:[~2025-07-02 23:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 10:43 [PATCH RFT v2] nfsd: provide locking for v4_end_grace NeilBrown
2025-07-02 7:03 ` Li Lingfeng
2025-07-02 9:38 ` NeilBrown
2025-07-02 12:48 ` Li Lingfeng
2025-07-02 13:56 ` Chuck Lever
2025-07-02 21:22 ` NeilBrown
2025-07-02 23:26 ` Chuck Lever [this message]
2025-12-02 12:34 ` Li Lingfeng
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=7de72319-95ce-46b8-8aa5-33fb211aaadc@oracle.com \
--to=chuck.lever@oracle.com \
--cc=Dai.Ngo@oracle.com \
--cc=jlayton@kernel.org \
--cc=lilingfeng3@huawei.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=tom@talpey.com \
/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