lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 3 Jun 2022 19:43:40 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-kernel@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, stable@...r.kernel.org, Olga Kornievskaia <aglo@...ch.edu>, Trond Myklebust <trond.myklebust@...merspace.com>, Anna Schumaker <Anna.Schumaker@...app.com> Subject: [PATCH 5.15 60/66] NFS: Memory allocation failures are not server fatal errors From: Trond Myklebust <trond.myklebust@...merspace.com> 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@...ch.edu> Fixes: 2dc23afffbca ("NFS: ENOMEM should also be a fatal error.") Cc: stable@...r.kernel.org Signed-off-by: Trond Myklebust <trond.myklebust@...merspace.com> Signed-off-by: Anna Schumaker <Anna.Schumaker@...app.com> Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org> --- fs/nfs/internal.h | 1 + 1 file changed, 1 insertion(+) --- a/fs/nfs/internal.h +++ b/fs/nfs/internal.h @@ -834,6 +834,7 @@ static inline bool nfs_error_is_fatal_on case 0: case -ERESTARTSYS: case -EINTR: + case -ENOMEM: return false; } return nfs_error_is_fatal(err);
Powered by blists - more mailing lists