From: Trond Myklebust <trondmy@kernel.org>
To: "Lukáš Hejtmánek" <xhejtman@ics.muni.cz>,
"Santosh Pradhan" <santosh.pradhan@gmail.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"salvet@ics.muni.cz" <salvet@ics.muni.cz>
Subject: Re: NFS stuck in nfs_lookup_revalidate
Date: Fri, 18 Jul 2025 17:02:51 -0700 [thread overview]
Message-ID: <7f27118fcc39a84400494549274edb78e455d4c2.camel@kernel.org> (raw)
In-Reply-To: <59D374DB-14C8-42F5-956F-C030AF614C69@ics.muni.cz>
On Fri, 2025-07-18 at 22:19 +0000, Lukáš Hejtmánek wrote:
> Hello,
>
> > On 4. 6. 2025, at 21:11, Zdenek Salvet <salvet@ics.muni.cz> wrote:
> >
> > On Thu, Jun 05, 2025 at 12:00:44AM +0530, Santosh Pradhan wrote:
> > > I am not sure but I vaguely remember that there was some similar
> > > issue and
> > > Neil introduced store_release_wake_up() which puts a full
> > > barrier smp_mb()
> > > before calling wake_up_var().
> > >
> > > index d0e0b435a843..e754e3e478a5 100644
> > > --- a/fs/nfs/dir.c
> > > +++ b/fs/nfs/dir.c
> > > @@ -1830,6 +1830,7 @@ static void unblock_revalidate(struct
> > > dentry *dentry)
> > > {
> > > /* store_release ensures wait_var_event() sees the update
> > > */
> > > smp_store_release(&dentry->d_fsdata, NULL);
> > > + smp_mb();
> > > wake_up_var(&dentry->d_fsdata);
> > > }
>
> any chance to get this into mainline? It seems that the current git
> master does not inlude smb_mb(); in this code.
>
>
I'm adding a fix that will go in to the next merge window.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trondmy@kernel.org, trond.myklebust@hammerspace.com
prev parent reply other threads:[~2025-07-19 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 11:57 NFS stuck in nfs_lookup_revalidate Lukáš Hejtmánek
2025-06-04 17:40 ` Anna Schumaker
[not found] ` <CAOuNp5kzbyVfbdumXJF3bb=RKxdE5P8aKJDeSoLtgEV9=9xU+g@mail.gmail.com>
2025-06-04 19:11 ` Zdenek Salvet
2025-07-18 22:19 ` Lukáš Hejtmánek
2025-07-19 0:02 ` Trond Myklebust [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=7f27118fcc39a84400494549274edb78e455d4c2.camel@kernel.org \
--to=trondmy@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=salvet@ics.muni.cz \
--cc=santosh.pradhan@gmail.com \
--cc=xhejtman@ics.muni.cz \
/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