[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <40aa347f-43eb-faf7-d6b7-dce6897f8a85@redhat.com>
Date: Thu, 24 Aug 2017 12:58:55 +0800
From: Ian Kent <ikent@...hat.com>
To: NeilBrown <neilb@...e.com>,
"viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>,
David Howells <dhowells@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: Jeff Layton <jlayton@...hat.com>,
Trond Myklebust <trondmy@...marydata.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mkoutny@...e.com" <mkoutny@...e.com>,
"linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
Subject: Re: Do we really need d_weak_revalidate???
On 24/08/17 12:07, NeilBrown wrote:
>
>
> The more precise details, that automount action for indirect automount
> points is not triggered when the 'browse' option is used, is probably
> not necessary.
>
> Ian: if you agree with that text, and Michael doesn't provide alternate
> evidence, I'll submit a formal patch for the man page.... or should we
> just wait until the patch actually lands?
So far only David commented about using ENOENT rather than EREMOTE.
I prefer ENOENT for this case myself and he didn't object when I
explained why, David, any concerns?
Al has been silent so far so either he hasn't seen it or he's ok with
it, Al, any concerns?
And I guess if there are no concerns there's a good chance Andrew is
ok with it for the next merge window, Andrew?
If everyone agrees then we could go ahead immediately so there's a
better chance of getting it into released man pages closer to the
change being merged.
Ian
Powered by blists - more mailing lists