From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: mtk.manpages@gmail.com, Andreas Dilger <adilger@dilger.ca>,
Neil Brown <neilb@suse.de>, linux-man <linux-man@vger.kernel.org>,
Mike Frysinger <vapier@gentoo.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: For review: open_by_handle_at(2) man page [v4]
Date: Fri, 04 Apr 2014 13:14:13 +0200 [thread overview]
Message-ID: <533E9405.9020803@gmail.com> (raw)
In-Reply-To: <8738htnzje.fsf@linux.vnet.ibm.com>
On 04/04/2014 12:45 PM, Aneesh Kumar K.V wrote:
> "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com> writes:
>> The process receiving the handle can later perform operations
>> on the symbolic link by converting the handle to a file descriptor using
>> .BR open_by_handle_at ()
>> with the
>> .BR O_PATH
>> flag, and then passing the file descriptor as the
>> .IR dirfd
>> argument in system calls such as
>> .BR readlinkat (2)
>> and
>> .BR fchownat (2).
>
>
> You may want to specify that one need to pass AT_EMPTY_PATH in case of
> fchownat ? readlinkat do take null names, because there is no flags
> argument. For syscalls that take flags, to make it operate on fd, one
> need to pass "" path name and a flag value of AT_EMPTY_PATH.
Thanks. However, those details are covered in (recent versions of) the
man pages for those system calls, and I'd prefer not to duplicate here.
Thanks also for your other reply re O_PATH/-ELOOP.
Otherwise, did all of the technical content in these pages look
accurate?
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2014-04-04 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 5:43 For review: open_by_handle_at(2) man page [v4] Michael Kerrisk (man-pages)
2014-04-04 10:40 ` Aneesh Kumar K.V
2014-04-04 10:45 ` Aneesh Kumar K.V
2014-04-04 11:14 ` Michael Kerrisk (man-pages) [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=533E9405.9020803@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=adilger@dilger.ca \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=neilb@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).