]> git.ipfire.org Git - thirdparty/linux.git/commit
netfs: when subreq is marked for retry, do not check if it faced an error
authorShyam Prasad N <sprasad@microsoft.com>
Sat, 31 Jan 2026 08:33:04 +0000 (14:03 +0530)
committerSteve French <stfrench@microsoft.com>
Sun, 8 Feb 2026 23:07:43 +0000 (17:07 -0600)
commit82e8885bd7633a36ee9050e6d7f348a4155eed5f
tree3aff640876af977d121dafdfac0ec9c2f34eff2e
parent16d480ed4990ed5aefb99c111dd14131a338e3c9
netfs: when subreq is marked for retry, do not check if it faced an error

The *_subreq_terminated functions today only process the NEED_RETRY
flag when the subreq was successful or failed with EAGAIN error.
However, there could be other retriable errors for network filesystems.

Avoid this by processing the NEED_RETRY irrespective of the error
code faced by the subreq. If it was specifically marked for retry,
the error code must not matter.

Acked-by: David Howells <dhowells@redhat.com>
Signed-off-by: Shyam Prasad N <sprasad@microsoft.com>
Signed-off-by: Steve French <stfrench@microsoft.com>
fs/netfs/read_collect.c
fs/netfs/read_retry.c
fs/netfs/write_collect.c
fs/netfs/write_issue.c