From: Wang Yugui <wangyugui@e16-tech.com>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: one more patch(nfsd: fix potential race in nfs4_find_file) for 6.1.83+ ?
Date: Tue, 02 Apr 2024 06:19:32 +0800 [thread overview]
Message-ID: <20240402061931.7D26.409509F4@e16-tech.com> (raw)
In-Reply-To: <E9D90677-6F0A-44BF-A7CC-771CEC8B41DE@oracle.com>
Hi,
>
> > On Apr 1, 2024, at 7:05?AM, Wang Yugui <wangyugui@e16-tech.com> wrote:
> >
> > Hi,
> >
> > We had 13 nfsd patches in 6.1.83, do we need one more patch(*1)?
> >
> > *1:
> > bd6aaf781dae :Jeff Layton: nfsd: fix potential race in nfs4_find_file
>
> This one went in after v6.2 (where I drew a line in
> the sand) and looked more like a clean-up than a bug fix.
>
> Is the kernel misbehaving? Why do you believe this one
> needs to be backported?
Yet not find any kernel misbehaving.
just fs/nfsd/filecache.c related.
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2024/04/02
prev parent reply other threads:[~2024-04-01 23:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 11:05 one more patch(nfsd: fix potential race in nfs4_find_file) for 6.1.83+ ? Wang Yugui
2024-04-01 13:47 ` Chuck Lever III
2024-04-01 22:19 ` Wang Yugui [this message]
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=20240402061931.7D26.409509F4@e16-tech.com \
--to=wangyugui@e16-tech.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/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