From: "zhangyi (F)" <yi.zhang@huawei.com>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, linux-aio@kvack.org,
linux-fsdevel@vger.kernel.org, bcrl@kvack.org,
viro@zeniv.linux.org.uk, jmoyer@redhat.com, arnd@arndb.de,
deepa.kernel@gmail.com, yi.zhang@huawei.com,
wangkefeng.wang@huawei.com
Subject: [PATCH] io_getevents.2: Add EINVAL for case of timeout parameter out of range
Date: Wed, 31 Jul 2019 11:03:13 +0800 [thread overview]
Message-ID: <1564542193-89171-1-git-send-email-yi.zhang@huawei.com> (raw)
io_[p]getevents syscall should return -EINVAL if timeout is out of
range, update description of this error return value.
Link: https://lore.kernel.org/lkml/1564451504-27906-1-git-send-email-yi.zhang@huawei.com/
Signed-off-by: zhangyi (F) <yi.zhang@huawei.com>
Cc: Jeff Moyer <jmoyer@redhat.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Deepa Dinamani <deepa.kernel@gmail.com>
---
man2/io_getevents.2 | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/man2/io_getevents.2 b/man2/io_getevents.2
index 0eb4b385e..5560bb8ee 100644
--- a/man2/io_getevents.2
+++ b/man2/io_getevents.2
@@ -73,8 +73,9 @@ Interrupted by a signal handler; see
.TP
.B EINVAL
\fIctx_id\fP is invalid.
-\fImin_nr\fP is out of range or \fInr\fP is
-out of range.
+\fImin_nr\fP is out of range or \fInr\fP is out of range, or
+\fItimeout\fP is out of range (\fItv_sec\fP was less than zero, or
+\fItv_nsec\fP was not less than 1,000,000,000).
.TP
.B ENOSYS
.BR io_getevents ()
--
2.20.1
--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org. For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next reply other threads:[~2019-07-31 3:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 3:03 zhangyi (F) [this message]
2020-04-16 12:12 ` [PATCH] io_getevents.2: Add EINVAL for case of timeout parameter out of range Michael Kerrisk (man-pages)
2020-04-16 12:56 ` zhangyi (F)
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=1564542193-89171-1-git-send-email-yi.zhang@huawei.com \
--to=yi.zhang@huawei.com \
--cc=arnd@arndb.de \
--cc=bcrl@kvack.org \
--cc=deepa.kernel@gmail.com \
--cc=jmoyer@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wangkefeng.wang@huawei.com \
/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).