All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. R. Okajima" <hooanon05g@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Jeff Layton <jlayton@primarydata.com>
Subject: Re: [PATCH] dcache: return -ESTALE not -EBUSY on distributed fs race
Date: Fri, 19 Dec 2014 11:46:26 +0900	[thread overview]
Message-ID: <6944.1418957186@jrobl> (raw)
In-Reply-To: <20141218231548.GF15665@dastard>


Dave Chinner:
> We use file handles on local filesystems. They have exactly the same
> semantics as NFS file handles and so local filesystems have the same
> ESTALE exposure as "distributed" filesystems to this problem. i.e:

It is reasonable.
But do you think ESTALE is good in case of __d_unalias()?


J. R. Okajima

  reply	other threads:[~2014-12-19  2:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17 19:59 [PATCH] dcache: return -ESTALE not -EBUSY on distributed fs race J. Bruce Fields
2014-12-17 20:01 ` J. Bruce Fields
2014-12-17 20:01   ` J. Bruce Fields
2014-12-18 15:50   ` J. R. Okajima
2014-12-18 15:58     ` J. Bruce Fields
2014-12-18 15:58       ` J. Bruce Fields
2014-12-18 16:27       ` J. R. Okajima
2014-12-18 16:27         ` J. R. Okajima
2014-12-18 17:32         ` Jeff Layton
2014-12-18 23:15         ` Dave Chinner
2014-12-18 23:15           ` Dave Chinner
2014-12-19  2:46           ` J. R. Okajima [this message]
2014-12-19 11:09             ` Jeff Layton
2014-12-19 11:09               ` Jeff Layton
2014-12-22  9:53               ` J. R. Okajima
  -- strict thread matches above, loose matches on Subject: below --
2015-02-10 15:55 J. Bruce Fields
2015-02-10 15:55 ` J. Bruce Fields
2015-02-18 15:03 ` J. Bruce Fields
2015-02-24 21:22   ` J. Bruce Fields
2015-02-24 21:22     ` J. Bruce Fields

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=6944.1418957186@jrobl \
    --to=hooanon05g@gmail.com \
    --cc=bfields@fieldses.org \
    --cc=david@fromorbit.com \
    --cc=jlayton@primarydata.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@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.