From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Matthew Dempsky <mdempsky-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: open(2) says O_DIRECTORY is Linux-specific
Date: Thu, 10 Apr 2014 21:14:25 +0200 [thread overview]
Message-ID: <5346ED91.9040306@gmail.com> (raw)
In-Reply-To: <CAF52+S5ATj7R-F=ni-S3M7ax4QrfN0wunvchQSuy-cqkYPNyow-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 04/08/2014 10:14 PM, Matthew Dempsky wrote:
> http://man7.org/linux/man-pages/man2/open.2.html
>
> O_DIRECTORY
> If pathname is not a directory, cause the open to fail. This
> flag is Linux-specific, and was added in kernel version
> 2.1.126, to avoid denial-of-service problems if opendir(3) is
> called on a FIFO or tape device.
>
> The "This flag is Linux-specific" bit is no longer true, since it was
> standardized by POSIX.1-2008 (as mentioned in the "CONFORMING TO"
> section later), and FreeBSD, NetBSD, and OpenBSD all implement it (at
> least according to their man pages). Perhaps saying "This flag was
> Linux-specific until standardized by POSIX.1-2008, and was added in
> ..." would be more accurate?
Hi Matthew,
Thanks for the report. That text is indeed crufty, but all that's needed
is to remove the piece saying that the flag is Linux-speciifc, since
elsewhere in the page it is explained that it is in POSIX.1-2008.
I've simply removed the words "is Linux-specific, and".
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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
parent reply other threads:[~2014-04-10 19:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAF52+S5ATj7R-F=ni-S3M7ax4QrfN0wunvchQSuy-cqkYPNyow-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
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=5346ED91.9040306@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mdempsky-F7+t8E8rja9g9hUCZPvPmw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.