From: Al Viro <viro@ZenIV.linux.org.uk>
To: "Ted Ts'o" <tytso@mit.edu>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
Mike Frysinger <vapier@gentoo.org>,
linux-man@vger.kernel.org, Richard Weinberger <richard@nod.at>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] open(2): document O_PATH
Date: Thu, 3 May 2012 14:20:25 +0100 [thread overview]
Message-ID: <20120503132025.GO6871@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20120503130707.GF18002@thunk.org>
On Thu, May 03, 2012 at 09:07:07AM -0400, Ted Ts'o wrote:
> On Thu, May 03, 2012 at 01:57:21PM +0530, Aneesh Kumar K.V wrote:
> >
> > fstat won't work, but fstatat with an empty path name would work. O_PATH
> > descriptors are suppose to be used as "location only descriptors".
> > We then extended the *at syscalls to work with EMPTY pathnames so that
> > O_PATH descriptors can be used with readlink, fchownat and fstatat().
> > This was done to enable us to do these operation on symlinks.
> > (65cfc6722361570bfe255698d9cd4dccaf47570d)
>
> Could you define explicitly what you mean by "EMPTY" pathnames?
"". Normally yields -EINVAL when used as a relative pathname in ...at()
syscalls.
next prev parent reply other threads:[~2012-05-03 13:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1335669917-23970-1-git-send-email-vapier@gentoo.org>
2012-04-29 21:39 ` [PATCH] open(2): document O_PATH 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 [this message]
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
2013-03-14 9:35 Michael Kerrisk (man-pages)
2013-07-20 11:40 ` Al Viro
2013-07-20 20:56 ` Michael Kerrisk
2013-07-22 8:46 ` Peter Schiffer
2013-07-22 10:45 ` Michael Kerrisk (man-pages)
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=20120503132025.GO6871@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=richard@nod.at \
--cc=tytso@mit.edu \
--cc=vapier@gentoo.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).