From: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 1/1] fcntl: F_GETFL: return value contains additional internal flags
Date: Fri, 25 Apr 2014 17:30:44 +0200 [thread overview]
Message-ID: <535A7FA4.1000408@gmx.de> (raw)
In-Reply-To: <CAKgNAkgi3XZY4v8JBPZjP=5sOmKpQPEMbaFJ8OSRnMW-+PyxLQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 25.04.2014 15:46, Michael Kerrisk (man-pages) wrote:
> Hi Heinrich,
>
> On Thu, Apr 24, 2014 at 10:05 PM, Heinrich Schuchardt
> <xypron.glpk-Mmb7MZpHnFY@public.gmane.org> wrote:
>> flags = fcntl(fd, F_GETFL);
>>
>> can return more flags than those defined in the open(2) manpage, e.g.
>> #define FMODE_NONOTIFY 0x1000000
>>
>> The manpage should point this out.
>>
>> Signed-off-by: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
>
> I think it might be good to mention a concrete example here. So, how
> about explicitly mentioning the FMODE_NONOTIFY and the fanotify(7) man
> page. Could you redraft?
Please, read my mail
Re: fanotify API: FMODE_NONOTIFY, FMODE_EXEC, FMODE_NOCMTIME
13.04.2014 16:05 (CEST)
http://www.spinics.net/lists/linux-man/msg05366.html
I mentioned that some other flags can be returned by fcntl, too. These
are not specific to fanotify. The examples given were
0x20 (FMODE_EXEC), and
0x800 (FMODE_NOCMTIME)
All relevant flags are defined in
include/uapi/asm-generic/fcntl.h
So would it not make more sense to relate to this include instead of
fanotify(7)?
I never got a reply to the question asked in aforementioned mail,
whether the observed behavior should be mentioned in the BUGS section of
fanotify(7).
Cheers
Heinrich
> Thanks,
>
> Michael
>
>
>> ---
>> man2/fcntl.2 | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/man2/fcntl.2 b/man2/fcntl.2
>> index fc1d3b3..0fd2d0a 100644
>> --- a/man2/fcntl.2
>> +++ b/man2/fcntl.2
>> @@ -180,6 +180,9 @@ The file status flags and their semantics are described in
>> Get the file access mode and the file status flags;
>> .I arg
>> is ignored.
>> +The return value contains the file status flags as described in
>> +.IR open (2).
>> +It may additionally contain status flags that are only used internally.
>> .TP
>> .BR F_SETFL " (\fIint\fP)"
>> Set the file status flags to the value specified by
>> --
>> 1.9.2
>>
>
>
>
--
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
prev parent reply other threads:[~2014-04-25 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 20:05 [PATCH 1/1] fcntl: F_GETFL: return value contains additional internal flags Heinrich Schuchardt
[not found] ` <1398369940-13673-1-git-send-email-xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
2014-04-25 13:46 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkgi3XZY4v8JBPZjP=5sOmKpQPEMbaFJ8OSRnMW-+PyxLQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-04-25 15:30 ` Heinrich Schuchardt [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=535A7FA4.1000408@gmx.de \
--to=xypron.glpk-mmb7mzphnfy@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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;
as well as URLs for NNTP newsgroup(s).