NFS: Memory allocation failures are not server fatal errors
commit 452284407c18d8a522c3039339b1860afa0025a8 upstream.
We need to filter out ENOMEM in nfs_error_is_fatal_on_server(), because
running out of memory on our client is not a server error.
Reported-by: Olga Kornievskaia <aglo@umich.edu>
Fixes: 2dc23afffb
("NFS: ENOMEM should also be a fatal error.")
Cc: stable@vger.kernel.org
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:

committed by
Greg Kroah-Hartman

parent
1d100fcc1d
commit
78a62e09d8
@@ -832,6 +832,7 @@ static inline bool nfs_error_is_fatal_on_server(int err)
|
|||||||
case 0:
|
case 0:
|
||||||
case -ERESTARTSYS:
|
case -ERESTARTSYS:
|
||||||
case -EINTR:
|
case -EINTR:
|
||||||
|
case -ENOMEM:
|
||||||
return false;
|
return false;
|
||||||
}
|
}
|
||||||
return nfs_error_is_fatal(err);
|
return nfs_error_is_fatal(err);
|
||||||
|
Reference in New Issue
Block a user