From: Zdenek Salvet <salvet@ics.muni.cz>
To: Santosh Pradhan <santosh.pradhan@gmail.com>
Cc: "Lukáš Hejtmánek" <xhejtman@ics.muni.cz>, linux-nfs@vger.kernel.org
Subject: Re: NFS stuck in nfs_lookup_revalidate
Date: Wed, 4 Jun 2025 21:11:05 +0200 [thread overview]
Message-ID: <aECaSYGt59HHgi7M@horn.ics.muni.cz> (raw)
In-Reply-To: <CAOuNp5kzbyVfbdumXJF3bb=RKxdE5P8aKJDeSoLtgEV9=9xU+g@mail.gmail.com>
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);
> }
Hello,
yes, upon rereading exact definition of smp_store_release(),
I am reasonably sure the comment is wrong and smp_mb() should be used,
it ensures the right ordering between store to d_fsdata and wait queue
data, not the smp_store_release(&dentry->d_fsdata,...).
Best regards,
Zdenek Salvet salvet@ics.muni.cz
Institute of Computer Science of Masaryk University, Brno, Czech Republic
and CESNET, z.s.p.o., Prague, Czech Republic
Phone: ++420-549 49 6534 Fax: ++420-541 212 747
----------------------------------------------------------------------------
Teamwork is essential -- it allows you to blame someone else.
next prev parent reply other threads:[~2025-06-04 19:22 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 [this message]
2025-07-18 22:19 ` Lukáš Hejtmánek
2025-07-19 0:02 ` Trond Myklebust
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=aECaSYGt59HHgi7M@horn.ics.muni.cz \
--to=salvet@ics.muni.cz \
--cc=linux-nfs@vger.kernel.org \
--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