Ensure mapping errors are reported only once
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest5 patches 1 replyIn review
- v25 patches 5 repliesSuperseded
- v12 patches 1 replySuperseded
Patches in v3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | NFS: Do not report EINTR/ERESTARTSYS as mapping errorsfs/ | +1 | 0 replies | |
| 2/5 | NFS: fsync() should report filesystem errors over EINTR/ERESTARTSYSfs/ | +5 | 0 replies | |
| 3/5 | NFS: Don't report ENOSPC write errors twicefs/ | +14 | 1 reply | |
| 4/5 | NFS: Do not report flush errors in nfs_write_end()fs/ | +2 | 0 replies | |
| 5/5 | NFS: Don't report errors from nfs_pageio_complete() more than oncefs/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
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