All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	adilger@dilger.ca, hch@lst.de
Subject: Re: [PATCH 1/2] fs: add a DCACHE_NEED_LOOKUP flag for d_flags V2
Date: Mon, 23 May 2011 12:13:07 -0400	[thread overview]
Message-ID: <4DDA8793.3010906@redhat.com> (raw)
In-Reply-To: <20110522021130.GI19987@ZenIV.linux.org.uk>

On 05/21/2011 10:11 PM, Al Viro wrote:
> On Fri, May 20, 2011 at 01:44:30PM -0400, Josef Bacik wrote:
>> +		if (unlikely(d_need_lookup(dentry))) {
>> +			if (nameidata_dentry_drop_rcu(nd, dentry))
>> +				return -ECHILD;
>> +			dput(dentry);
>> +			dentry = NULL;
>> +			goto retry;
> 
> Yecchhh...  How about simple goto unlazy; here instead and doing the rest
> there?  Especially since you have the same kind of thing elsewhere in the
> same sucker.  It had been bloody painful to untangle that thing; let's not
> add to the rat's nest that still remains...

This is where I was a little confused, which is why I added this code.  It
seems that having goto unlazy; will mean that we will come down to this
section

if (unlikely(status  <= 0 )) {
	if (status < 0) {
		dput(dentry);
		return status;
	}
        if (!d_invalidate(dentry)) {
		dput(dentry);
		dentry = NULL;
		need_reval = 1;
		goto retry;
	}
}

and d_invalidate will unhash us so we won't find our new dentry in the cache
which makes this whole exercise useless.  Is there a different way you'd
like
this cleaned up?  Thanks,

Josef


  reply	other threads:[~2011-05-23 16:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-20 17:44 [PATCH 1/2] fs: add a DCACHE_NEED_LOOKUP flag for d_flags V2 Josef Bacik
2011-05-20 17:44 ` [PATCH 2/2] Btrfs: load the key from the dir item in readdir into a fake dentry V2 Josef Bacik
2011-05-22  2:11 ` [PATCH 1/2] fs: add a DCACHE_NEED_LOOKUP flag for d_flags V2 Al Viro
2011-05-23 16:13   ` Josef Bacik [this message]
2011-05-26 10:35     ` Al Viro

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=4DDA8793.3010906@redhat.com \
    --to=josef@redhat.com \
    --cc=adilger@dilger.ca \
    --cc=hch@lst.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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.