Skip to content

Ensure mapping errors are reported only once

[email protected] linux-nfs 3 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v3 Latest5 patches 1 replyIn review
  2. v25 patches 5 repliesSuperseded
  3. v12 patches 1 replySuperseded

Patches in v3 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/5NFS: Do not report EINTR/ERESTARTSYS as mapping errorsfs/nfs/write.c+1 -10 replies
2/5NFS: fsync() should report filesystem errors over EINTR/ERESTARTSYSfs/nfs/file.c+5 -40 replies
3/5NFS: Don't report ENOSPC write errors twicefs/nfs/file.c+14 -201 reply
4/5NFS: Do not report flush errors in nfs_write_end()fs/nfs/file.c+2 -50 replies
5/5NFS: Don't report errors from nfs_pageio_complete() more than oncefs/nfs/write.c+1 -80 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.

Read the v3 thread

Cover letter [PATCH v3 0/5] Ensure mapping errors are reported only once

From: Trond Myklebust <[email protected]>

The expectation since Linux 4.13 has been that EIO errors are always reported in fsync(), whether or not they were detected and reported earlier.
On the other hand, ENOSPC errors are reported as soon as detected, and should only be reported once.

--
v3: minor correctness fixes

Trond Myklebust (5):
NFS: Do not report EINTR/ERESTARTSYS as mapping errors
NFS: fsync() should report filesystem errors over EINTR/ERESTARTSYS
NFS: Don't report ENOSPC write errors twice
NFS: Do not report flush errors in nfs_write_end()
NFS: Don't report errors from nfs_pageio_complete() more than once

 fs/nfs/file.c  | 50 +++++++++++++++++++++-----------------------------
 fs/nfs/write.c | 11 ++---------
 2 files changed, 23 insertions(+), 38 deletions(-)
Signature · 1 line
2.36.1