From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Stephan Mueller
<stephan.mueller-fwYZOkdEjagAvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: open_by_handle_at(2) and name_to_handle_at(2)
Date: Mon, 12 Sep 2011 15:29:13 -0400 [thread overview]
Message-ID: <20110912192913.GA15182@infradead.org> (raw)
In-Reply-To: <4E6E547F.2000104-fwYZOkdEjagAvxtiuMwx3w@public.gmane.org>
On Mon, Sep 12, 2011 at 08:50:39PM +0200, Stephan Mueller wrote:
> as the actual file handle can have a varying size. The variable of
> .I handle_type
> specifies how the file within the filesystem is encoded. This value
> is set to one of the following values:
This has absolutely no business in the man page. As far as userspace
is concerned this simply is an opaque handle freely chose by the
file system. The only reason we have an emum for them is to make
it easier to follow them on the wire using tools like wireshark.
The man page should probably also mentioned that these systems calls
are optinal and might not be present on modern kernel in case they
have been disabled during configuration.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-09-12 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 20:48 open_by_handle_at(2) and name_to_handle_at(2) Stephan Mueller
[not found] ` <4E6A7B89.7070708-fwYZOkdEjagAvxtiuMwx3w@public.gmane.org>
2011-09-12 18:50 ` Stephan Mueller
[not found] ` <4E6E547F.2000104-fwYZOkdEjagAvxtiuMwx3w@public.gmane.org>
2011-09-12 19:29 ` Christoph Hellwig [this message]
[not found] ` <20110912192913.GA15182-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2011-09-12 19:37 ` Stephan Mueller
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=20110912192913.GA15182@infradead.org \
--to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=stephan.mueller-fwYZOkdEjagAvxtiuMwx3w@public.gmane.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