Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@manguebit.org>
To: linux-cifs@vger.kernel.org, netfs@lists.linux.dev,
	David Howells <dhowells@redhat.com>
Cc: "Namjae Jeon" <linkinjeon@kernel.org>,
	"Ronnie Sahlberg" <ronniesahlberg@gmail.com>,
	"Shyam Prasad N" <sprasad@microsoft.com>,
	"Tom Talpey" <tom@talpey.com>,
	"Bharath SM" <bharathsm@microsoft.com>,
	"Christian Brauner" <brauner@kernel.org>,
	"Iván Ezequiel Rodriguez" <ivanrwcm25@gmail.com>,
	stable@vger.kernel.org
Subject: [PATCH v7 02/19] netfs: preserve prepare_write errno on reissue
Date: Fri,  6 Nov 2026 20:18:10 -0300	[thread overview]
Message-ID: <20261106231827.2604956-3-pc@manguebit.org> (raw)
In-Reply-To: <20261106231827.2604956-1-pc@manguebit.org>

From: Iván Ezequiel Rodriguez <ivanrwcm25@gmail.com>

prepare_write() may call netfs_prepare_write_failed() (FAILED + errno)
before write_retry calls netfs_reissue_write().  Clearing subreq->error
to 0 for a clean I/O reissue (82e8885bd763) then makes
netfs_do_issue_write() terminate with 0.  The collector copies
front->error into stream->error and mapping_set_error(), which ignores
0, so writeback failure is silent.

Skip clearing error when NETFS_SREQ_FAILED is already set;
do_issue_write() already terminates FAILED subrequests.

Fixes: 82e8885bd763 ("netfs: when subreq is marked for retry, do not check if it faced an error")
Signed-off-by: Iván Ezequiel Rodriguez <ivanrwcm25@gmail.com>
Signed-off-by: Paulo Alcantara <pc@manguebit.org>
Cc: stable@vger.kernel.org
---
 fs/netfs/write_issue.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/fs/netfs/write_issue.c b/fs/netfs/write_issue.c
index b8237e1314d8..f23364116421 100644
--- a/fs/netfs/write_issue.c
+++ b/fs/netfs/write_issue.c
@@ -268,7 +268,9 @@ void netfs_reissue_write(struct netfs_io_stream *stream,
 	iov_iter_truncate(&subreq->io_iter, size);
 
 	subreq->retry_count++;
-	subreq->error = 0;
+	/* Keep prepare_write() errno; do_issue_write() terminates FAILED. */
+	if (!test_bit(NETFS_SREQ_FAILED, &subreq->flags))
+		subreq->error = 0;
 	__clear_bit(NETFS_SREQ_MADE_PROGRESS, &subreq->flags);
 	__set_bit(NETFS_SREQ_IN_PROGRESS, &subreq->flags);
 	netfs_stat(&netfs_n_wh_retry_write_subreq);
-- 
2.56.0


  parent reply	other threads:[~2026-11-06 23:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 23:18 [PATCH v7 00/19] smb: client: fix data loss in writeback Paulo Alcantara
2026-11-06 23:18 ` [PATCH v7 01/19] smb: client: don't write back through O_DIRECT handles Paulo Alcantara
2026-11-06 23:18 ` Paulo Alcantara [this message]
2026-11-06 23:18 ` [PATCH v7 03/19] netfs: keep the prepare_read errno when abandoning read retries Paulo Alcantara
2026-11-06 23:18 ` [PATCH v7 04/19] netfs: don't hang a read whose retry is abandoned Paulo Alcantara
2026-11-06 23:18 ` [PATCH v7 05/19] smb: client: let umount -f abort retried reads and writes Paulo Alcantara
2026-11-06 23:18 ` [PATCH v7 06/19] smb: client: don't give up writeback on the first replayable error Paulo Alcantara
2026-11-06 23:18 ` [PATCH v7 07/19] smb: client: don't retry failed writes forever regardless of mount options Paulo Alcantara
2026-11-06 23:18 ` [PATCH v7 08/19] smb: client: don't spend read retries on reads cut short by a reconnect Paulo Alcantara
2026-11-06 23:18 ` [PATCH v7 09/19] smb: client: don't block dying tasks waiting for writeback on close Paulo Alcantara
2026-11-06 23:18 ` [PATCH v7 10/19] smb: client: issue writes from a worker if the task is dying Paulo Alcantara
2026-11-06 23:18 ` [PATCH v7 11/19] smb: client: don't fail writeback preparation " Paulo Alcantara
2026-11-06 23:18 ` [PATCH v7 12/19] smb: client: retry writeback on interrupts and allocation failures Paulo Alcantara
2026-11-06 23:18 ` [PATCH v7 13/19] smb: client: don't block dying tasks waiting for writeback on fsync Paulo Alcantara
2026-11-06 23:18 ` [PATCH v7 14/19] smb: client: retry writes that couldn't be issued due to a reconnect Paulo Alcantara
2026-11-06 23:18 ` [PATCH v7 15/19] smb: client: retry writeback after losing the connection, share or handle Paulo Alcantara
2026-11-06 23:18 ` [PATCH v7 16/19] smb: client: let umount -f stop waiting for reconnects on hard mounts Paulo Alcantara
2026-11-06 23:18 ` [PATCH v7 17/19] smb: client: don't replay handle reopens inside SMB2_open() Paulo Alcantara
2026-11-06 23:18 ` [PATCH v7 18/19] smb: client: fail writeback sends and reopens fast when the server is gone Paulo Alcantara
2026-11-06 23:18 ` [PATCH v7 19/19] smb: client: stop reconnecting and replaying during a forced unmount Paulo Alcantara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261106231827.2604956-3-pc@manguebit.org \
    --to=pc@manguebit.org \
    --cc=bharathsm@microsoft.com \
    --cc=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=ivanrwcm25@gmail.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=netfs@lists.linux.dev \
    --cc=ronniesahlberg@gmail.com \
    --cc=sprasad@microsoft.com \
    --cc=stable@vger.kernel.org \
    --cc=tom@talpey.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox