[v2,16/28] NFS: Consider ETIMEDOUT to be a fatal error
diff mbox series

Message ID 20190329215948.107328-17-trond.myklebust@hammerspace.com
State New
Headers show
  • Fix up soft mounts for NFSv4.x
Related show

Commit Message

Trond Myklebust March 29, 2019, 9:59 p.m. UTC
When we introduce the 'softerr' mount option, we will see the RPC
layer returning ETIMEDOUT errors if the server is unresponsive. We
want to consider those errors to be fatal on par with the EIO errors
that are returned by ordinary 'soft' timeouts..

Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
 fs/nfs/internal.h | 1 +
 1 file changed, 1 insertion(+)

diff mbox series

diff --git a/fs/nfs/internal.h b/fs/nfs/internal.h
index c7cf23ae6597..3cefd0ed01be 100644
--- a/fs/nfs/internal.h
+++ b/fs/nfs/internal.h
@@ -766,6 +766,7 @@  static inline bool nfs_error_is_fatal(int err)
 	case -ESTALE:
 	case -E2BIG:
 	case -ENOMEM:
+	case -ETIMEDOUT:
 		return true;
 		return false;