All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sheng Yong <shyodx1989@163.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, zhangshiming5@huawei.com,
	yuchao0@huawei.com, jaegeuk@kernel.org, chao@kernel.org
Subject: Re: Question: d_revalidate in rcu-walk
Date: Sun, 4 Sep 2016 16:46:09 +0800	[thread overview]
Message-ID: <57CBDF51.9070009@163.com> (raw)
In-Reply-To: <20160903130312.GC2356@ZenIV.linux.org.uk>


Thanks for your reply. There is something wrong with my mail client. It 
sent an empty email which I don't know why :( I hope it works this time.
在 2016/9/3 21:03, Al Viro 写道:
> On Sat, Sep 03, 2016 at 06:46:05PM +0800, shyodx1989 wrote:
>
>>
>> But most filesystems, which have d_revalidate, return -ECHILD if LOOKUP_RCU is set instead of
>> checking if it is safe for rcu-walk.
>
> For a good and simple reason that the work they would have to do in their
> ->d_revalidate() can't be done without blocking.  Which can't be done under
> rcu_read_lock(), thus the "sorry, you have to leave RCU mode for that", aka
> -ECHILD.

So, basically, ECHILD does not care about wheter d_inode, d_flags or 
other d_xxx members are updated or invalidated. If d_revalidate is not 
blocked, thus the task will not be switched out to break grace period, 
it is safe to call d_revalidate in RCU mode. And during rcu-walk, the 
dentry may be out of date, the seqcount could help to detect if someone 
is updating or using the dentry.

>
>> However commit 5c0f360b083fb33d05d1bff4b138b82d715eb419
>> "jfs_ci_revalidate() is safe from RCU mode" removes the check. So why is jfs_ci_revalidate safe in
>> RCU  mode
>
> Because JFS ->d_revalidate() doesn't need anything blocking.
>
>> and if we only check d_inode (like the following code), what should we care about to
>> tell if d_revalidate is safe for rcu-walk or not and? Ref-walk is much slower than rcu-walk, maybe
>> it's better not to return -ECHILD directly if not necessary.
>>
>>
>> d_revalidate(dentry, flags)
>> {
>>          if (flags & LOOKUP_RCU)
>>                  return -ECHILD
>>          if (!d_inode_rcu(dentry))
>>                  return 0;
>>          return 1;
>> }
>
> Huh?  Which filesystem would that be?  Sure, in such case -ECHILD is pointless;
> who does that?  Some of them might be possible to drop ECHILD, but that needs
> some care.  Note, BTW, that things like dput() are blocking, so the things like
> trying to grab parent, etc. can get tricky.

In fact, there are no filesystems do that. I just wanted to revalidate 
negative dentries during lookup for my own test, and was wondering why 
JFS behaves different with other local filesystems.

thanks,
Sheng

>
> Which ->d_revalidate() instance do you have in mind?
>


      parent reply	other threads:[~2016-09-04  9:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <60d375df.47a9.156efa7c83a.Coremail.shyodx1989@163.com>
2016-09-03 12:23 ` Question: d_revalidate in rcu-walk shyodx1989
2016-09-03 13:03 ` Al Viro
2016-09-04  8:14   ` shyodx1989
2016-09-04  8:46   ` Sheng Yong [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=57CBDF51.9070009@163.com \
    --to=shyodx1989@163.com \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    --cc=yuchao0@huawei.com \
    --cc=zhangshiming5@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.