From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Doug Goldstein <cardoe-VPKZcK2rSRzQT0dZR+AlfA@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] Add EINVAL to errors list of open(2)
Date: Mon, 02 Sep 2013 07:50:20 +0200 [thread overview]
Message-ID: <5224271C.5030709@gmail.com> (raw)
In-Reply-To: <1376686667-6686-1-git-send-email-cardoe-VPKZcK2rSRzQT0dZR+AlfA@public.gmane.org>
On 08/16/13 22:57, Doug Goldstein wrote:
> EINVAL can be returned by open(2) when the underlying filesystem doesn't
> support O_DIRECT. It is documented in the NOTES section but this patch
> adds it to the list of possible errors.
Applied. Thanks.
Cheers,
Michael
> ---
> man2/open.2 | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/man2/open.2 b/man2/open.2
> index 9ebc0a0..93a9e7d 100644
> --- a/man2/open.2
> +++ b/man2/open.2
> @@ -611,6 +611,13 @@ While blocked waiting to complete an open of a slow device
> the call was interrupted by a signal handler; see
> .BR signal (7).
> .TP
> +.B EINVAL
> +The filesystem does not support the
> +.BR O_DIRECT
> +flag. See
> +.BR NOTES
> +for more information.
> +.TP
> .B EISDIR
> .I pathname
> refers to a directory and the access requested involved writing
>
--
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:[~2013-09-02 5:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 20:57 [PATCH] Add EINVAL to errors list of open(2) Doug Goldstein
[not found] ` <1376686667-6686-1-git-send-email-cardoe-VPKZcK2rSRzQT0dZR+AlfA@public.gmane.org>
2013-09-02 5:50 ` 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=5224271C.5030709@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=cardoe-VPKZcK2rSRzQT0dZR+AlfA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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).