From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Mathnerd314 <mathnerd314.gph@gmail.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-man@vger.kernel.org, mtk.manpages@gmail.com,
linux-fsdevel@vger.kernel.org
Subject: Re: EINTR for fsync(2)
Date: Tue, 1 Feb 2022 15:48:40 +0100 [thread overview]
Message-ID: <a01a4f9a-da28-1135-080d-568de19e3d85@gmail.com> (raw)
In-Reply-To: <Yfh/E5i/oqhe6KsQ@casper.infradead.org>
Hi Mathnerd314, Matthew,
On 2/1/22 01:30, Matthew Wilcox wrote:
[...]
> So while it's worth adding EINTR to the man page, I don't think it's
> worth going through an exercise of trying to add every possible
> errno to every syscall.
>
Okay. I documented this error.
Thanks,
Alex
---
fsync.2: ERRORS: Document EINTR
Reported-by: Mathnerd314 <mathnerd314.gph@gmail.com>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
Cc: <linux-fsdevel@vger.kernel.org>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>
diff --git a/man2/fsync.2 b/man2/fsync.2
index 0f070ed2c..c79723ed8 100644
--- a/man2/fsync.2
+++ b/man2/fsync.2
@@ -126,6 +126,10 @@ is set to indicate the error.
.I fd
is not a valid open file descriptor.
.TP
+.B EINTR
+The function was interrupted by a signal; see
+.BR signal (7).
+.TP
.B EIO
An error occurred during synchronization.
This error may relate to data written to some other file descriptor
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
prev parent reply other threads:[~2022-02-01 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADVL9rE70DK+gWn-pbHXy6a+5sdkHzFg_xJ9phhQkRapTUJ_zg@mail.gmail.com>
2022-01-31 20:44 ` EINTR for fsync(2) Alejandro Colomar (man-pages)
2022-02-01 0:30 ` Matthew Wilcox
2022-02-01 14:48 ` Alejandro Colomar (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=a01a4f9a-da28-1135-080d-568de19e3d85@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mathnerd314.gph@gmail.com \
--cc=mtk.manpages@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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).