linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: NeilBrown <neilb@suse.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC][PATCH] fix breakage caused by d_find_alias() semantics change
Date: Sun, 13 May 2018 23:17:33 +0100	[thread overview]
Message-ID: <20180513221733.GX30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <87h8nb8b9j.fsf@notabene.neil.brown.name>

On Mon, May 14, 2018 at 08:02:32AM +1000, NeilBrown wrote:
 
> Could you say *which* file systems?  That would make it easier to
> understand the bigger picture.

Anything that uses pathname-based protocols...

      reply	other threads:[~2018-05-13 22:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-13 15:51 [RFC][PATCH] fix breakage caused by d_find_alias() semantics change Al Viro
2018-05-13 18:35 ` Linus Torvalds
2018-05-13 18:56   ` Al Viro
2018-05-13 18:59     ` Linus Torvalds
2018-05-13 19:48       ` Al Viro
2018-05-13 20:24         ` Linus Torvalds
2018-05-13 22:02         ` NeilBrown
2018-05-13 22:17           ` Al Viro [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=20180513221733.GX30522@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=neilb@suse.com \
    --cc=torvalds@linux-foundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).