From: Michael Kerrisk <mtk.manpages@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
Mike Frysinger <vapier@gentoo.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Peter Schiffer <pschiffe@redhat.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
linux-man <linux-man@vger.kernel.org>,
benjamin@python.org
Subject: Re: [PATCH] open(2): document O_PATH
Date: Sat, 20 Jul 2013 22:56:55 +0200 [thread overview]
Message-ID: <51EAF997.2090300@gmail.com> (raw)
In-Reply-To: <20130720114017.GA2118@ZenIV.linux.org.uk>
On 07/20/13 13:40, Al Viro wrote:
> On Thu, Mar 14, 2013 at 10:35:59AM +0100, Michael Kerrisk (man-pages) wrote:
>> Hello Al et al,
>>
>> Documenting O_PATH fell by the wayside last year
>> (http://thread.gmane.org/gmane.linux.man/2790) as I got distracted
>> with other tasks. A recent prod or two have reminded me restart this.
>> I have the following patch queued to document O_PATH.
>>
>> Could you please review. I've provided the O_PATH doc both as
>> formatted text, for ease of reviewing, and as a patch and entire file
>> (attached).
>
> Seems to be mostly correct; the only thing missing is that F_GETFL is also
> allowed (and return value will contain O_PATH for such descriptors). Had
> been there since the very beginning...
Thanks, Al. I have added that piece.
Cheers,
Michael
next prev parent reply other threads:[~2013-07-20 21:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 9:35 [PATCH] open(2): document O_PATH Michael Kerrisk (man-pages)
2013-07-20 11:40 ` Al Viro
2013-07-20 20:56 ` Michael Kerrisk [this message]
2013-07-22 8:46 ` Peter Schiffer
2013-07-22 10:45 ` Michael Kerrisk (man-pages)
[not found] <1335669917-23970-1-git-send-email-vapier@gentoo.org>
2012-04-29 21:39 ` Michael Kerrisk (man-pages)
2012-04-30 7:39 ` Aneesh Kumar K.V
2012-04-30 11:44 ` Ted Ts'o
2012-05-03 6:48 ` Michael Kerrisk (man-pages)
2012-05-03 8:27 ` Aneesh Kumar K.V
2012-05-03 13:07 ` Ted Ts'o
2012-05-03 13:20 ` Al Viro
2012-05-06 1:00 ` H. Peter Anvin
2012-05-03 6:47 ` Michael Kerrisk (man-pages)
2012-05-03 14:04 ` Aneesh Kumar K.V
2012-05-03 14:11 ` Al Viro
2012-05-05 11:31 ` Michael Kerrisk (man-pages)
2013-01-08 18:52 ` 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=51EAF997.2090300@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=benjamin@python.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=pschiffe@redhat.com \
--cc=tytso@mit.edu \
--cc=vapier@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox