summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTrond Myklebust <trondmy@gmail.com>2019-04-07 19:59:02 +0200
committerAnna Schumaker <Anna.Schumaker@Netapp.com>2019-04-25 20:18:14 +0200
commit14bebe3c90b326d2a0df78aed5e9de090c71d878 (patch)
tree8334eeff8fb57a91a64a0453c62766e252135b45
parentNFS: Add a mount option "softerr" to allow clients to see ETIMEDOUT errors (diff)
downloadlinux-14bebe3c90b326d2a0df78aed5e9de090c71d878.tar.xz
linux-14bebe3c90b326d2a0df78aed5e9de090c71d878.zip
NFS: Don't interrupt file writeout due to fatal errors
When flushing out dirty pages, the fact that we may hit fatal errors is not a reason to stop writeback. Those errors are reported through fsync(), not through the flush mechanism. Fixes: a6598813a4c5b ("NFS: Don't write back further requests if there...") Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com> Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
-rw-r--r--fs/nfs/write.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/nfs/write.c b/fs/nfs/write.c
index f3ebabaa291d..9198a23bb58b 100644
--- a/fs/nfs/write.c
+++ b/fs/nfs/write.c
@@ -647,7 +647,7 @@ out:
return ret;
out_launder:
nfs_write_error_remove_page(req);
- return ret;
+ return 0;
}
static int nfs_do_writepage(struct page *page, struct writeback_control *wbc,