public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: milan.opensource@gmail.com
To: mtk.manpages@gmail.com
Cc: linux-kernel@vger.kernel.org, Milan Shah <milan.opensource@gmail.com>
Subject: [PATCH] fsync.2: ERRORS: add EIO and ENOSPC
Date: Sat, 29 Aug 2020 12:43:06 +0530	[thread overview]
Message-ID: <1598685186-27499-1-git-send-email-milan.opensource@gmail.com> (raw)

From: Milan Shah <milan.opensource@gmail.com>

This Fix addresses Bug 194757.
Ref: https://bugzilla.kernel.org/show_bug.cgi?id=194757
---
 man2/fsync.2 | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/man2/fsync.2 b/man2/fsync.2
index 96401cd..f38b3e4 100644
--- a/man2/fsync.2
+++ b/man2/fsync.2
@@ -186,6 +186,19 @@ In these cases disk caches need to be disabled using
 or
 .BR sdparm (8)
 to guarantee safe operation.
+
+When
+.BR fsync ()
+or
+.BR fdatasync ()
+returns
+.B EIO
+or
+.B ENOSPC
+any error flags on pages in the file mapping are cleared, so subsequent synchronisation attempts
+will return without error. It is
+.I not
+safe to retry synchronisation and assume that a non-error return means prior writes are now on disk.
 .SH SEE ALSO
 .BR sync (1),
 .BR bdflush (2),
-- 
2.7.4


             reply	other threads:[~2020-08-29  7:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-29  7:13 milan.opensource [this message]
2020-09-07  7:11 ` [PATCH] fsync.2: ERRORS: add EIO and ENOSPC Michael Kerrisk (man-pages)
2020-09-08 11:27   ` Jan Kara
2020-09-08 16:10     ` Jeff Layton
2020-09-09 22:50       ` NeilBrown
2020-09-08 19:44     ` Jeff Layton
2020-09-09 10:53       ` Michael Kerrisk (man-pages)
2020-09-09 23:04       ` NeilBrown
2020-09-10 17:42         ` Jeff Layton
2020-09-16 23:25           ` NeilBrown
2020-09-17  7:01             ` Michael Kerrisk (man-pages)
2020-09-09 10:52     ` Michael Kerrisk (man-pages)
2020-09-09 11:21       ` Jan Kara
2020-09-09 11:58         ` Michael Kerrisk (man-pages)
2020-09-09 14:14           ` Jan Kara

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=1598685186-27499-1-git-send-email-milan.opensource@gmail.com \
    --to=milan.opensource@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@gmail.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