From: NeilBrown <neilb@suse.com>
To: "Michael Kerrisk \(man-pages\)" <mtk.manpages@gmail.com>
Cc: Ian Kent <ikent@redhat.com>, Jeff Layton <jlayton@redhat.com>,
Trond Myklebust <trondmy@primarydata.com>,
"viro\@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mkoutny\@suse.com" <mkoutny@suse.com>,
"linux-nfs\@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-fsdevel\@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH manpages] stat.2: correct AT_NO_AUTOMOUNT text and general revisions.
Date: Fri, 15 Sep 2017 08:25:23 +1000 [thread overview]
Message-ID: <87r2v89auk.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <CAKgNAkinKkG8cR1ng0V3K1D9QNQ9MSeNkPpvpeGSUd5RqFiwSw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
On Thu, Sep 14 2017, Michael Kerrisk (man-pages) wrote:
> Hi Neil,
>
> On 25 August 2017 at 07:32, NeilBrown <neilb@suse.com> wrote:
>>
>> Expand on the relationship between fstatat() and the other
>> three functions, and improve the description of AT_NO_AUTOMOUNT.
>> Specifically, both stat() and lstat() act the same way
>> with respect to automounts, and that behavior matches
>> fstatat with the AT_NO_AUTOMOUNT flag.
>>
>> The text in the NOTES is removed and places with the text for
>> AT_NO_AUTOMOUNT to improve cohesion.
>>
>> New text for a difference to be introduced in 4.14.
>
> Has the 4.14 piece gone in?
>
Yes.
Commit: 42f461482178 ("autofs: fix AT_NO_AUTOMOUNT not being honored")
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-09-14 22:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 4:31 Do we really need d_weak_revalidate??? NeilBrown
2017-08-11 5:55 ` Trond Myklebust
2017-08-11 11:01 ` Jeff Layton
2017-08-13 23:36 ` NeilBrown
2017-08-14 10:10 ` Jeff Layton
2017-08-16 2:43 ` NeilBrown
2017-08-16 11:34 ` Jeff Layton
2017-08-16 23:47 ` NeilBrown
2017-08-17 2:20 ` Ian Kent
2017-08-18 5:24 ` NeilBrown
2017-08-18 6:47 ` Ian Kent
2017-08-18 6:55 ` Ian Kent
2017-08-21 6:23 ` NeilBrown
2017-08-21 6:32 ` Ian Kent
2017-08-21 7:46 ` NeilBrown
2017-08-23 1:06 ` NeilBrown
2017-08-23 2:32 ` Ian Kent
2017-08-23 2:40 ` Ian Kent
2017-08-23 2:54 ` Ian Kent
2017-08-23 7:51 ` Ian Kent
2017-08-24 3:21 ` NeilBrown
2017-08-24 4:35 ` Ian Kent
2017-08-24 4:07 ` NeilBrown
2017-08-24 4:47 ` Ian Kent
2017-08-24 4:58 ` Ian Kent
2017-08-24 11:03 ` Michael Kerrisk (man-pages)
2017-08-25 0:05 ` Ian Kent
2017-08-25 5:32 ` [PATCH manpages] stat.2: correct AT_NO_AUTOMOUNT text and general revisions NeilBrown
2017-09-14 13:38 ` Michael Kerrisk (man-pages)
2017-09-14 22:25 ` NeilBrown [this message]
2017-09-16 13:11 ` Michael Kerrisk (man-pages)
2017-09-08 15:15 ` Do we really need d_weak_revalidate??? David Howells
2017-08-13 23:29 ` NeilBrown
2017-08-24 6:34 ` NeilBrown
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=87r2v89auk.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=dhowells@redhat.com \
--cc=hpa@zytor.com \
--cc=ikent@redhat.com \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mkoutny@suse.com \
--cc=mtk.manpages@gmail.com \
--cc=trondmy@primarydata.com \
--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 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).