public inbox for linux-cifs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: nspmangalore@gmail.com
Cc: dhowells@redhat.com, linux-cifs@vger.kernel.org,
	smfrench@gmail.com, pc@manguebit.com, bharathsm@microsoft.com,
	Shyam Prasad N <sprasad@microsoft.com>
Subject: Re: [PATCH 1/4] netfs: when subreq is marked for retry, do not check if it faced an error
Date: Wed, 21 Jan 2026 23:18:51 +0000	[thread overview]
Message-ID: <1652302.1769037531@warthog.procyon.org.uk> (raw)
In-Reply-To: <20260120062152.628822-1-sprasad@microsoft.com>

nspmangalore@gmail.com wrote:

> @@ -547,13 +547,15 @@ void netfs_read_subreq_terminated(struct netfs_io_subrequest *subreq)
>  	}
>  
>  	if (unlikely(subreq->error < 0)) {
> -		trace_netfs_failure(rreq, subreq, subreq->error, netfs_fail_read);
>  		if (subreq->source == NETFS_READ_FROM_CACHE) {
>  			netfs_stat(&netfs_n_rh_read_failed);
>  			__set_bit(NETFS_SREQ_NEED_RETRY, &subreq->flags);
>  		} else {
>  			netfs_stat(&netfs_n_rh_download_failed);
> -			__set_bit(NETFS_SREQ_FAILED, &subreq->flags);
> +			if (!test_bit(NETFS_SREQ_NEED_RETRY, &subreq->flags)) {
> +				__set_bit(NETFS_SREQ_FAILED, &subreq->flags);
> +				trace_netfs_failure(rreq, subreq, subreq->error, netfs_fail_read);
> +			}
>  		}
>  		trace_netfs_rreq(rreq, netfs_rreq_trace_set_pause);
>  		set_bit(NETFS_RREQ_PAUSE, &rreq->flags);

I think I suggested moving the check for NETFS_SREQ_NEED_RETRY up in the
function - above any checks of subreq->error, but after the initial stat
counting.

Ditto for netfs_write_subrequest_terminated().  Actually, the
transferred_or_error argument of that should be got rid of and the filesystem
update the subreq->error and subreq->transferred fields directly as for reads.

I can poke at this tomorrow if you want.

David


  parent reply	other threads:[~2026-01-21 23:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20  6:21 [PATCH 1/4] netfs: when subreq is marked for retry, do not check if it faced an error nspmangalore
2026-01-20  6:21 ` [PATCH 2/4] netfs: avoid double increment of retry_count in subreq nspmangalore
2026-01-21 23:23   ` David Howells
2026-01-20  6:21 ` [PATCH 3/4] cifs: Initialize cur_sleep value if not already done nspmangalore
2026-01-21 23:28   ` David Howells
2026-01-20  6:21 ` [PATCH 4/4] cifs: make retry logic in read/write path consistent with other paths nspmangalore
2026-01-20 11:32   ` kernel test robot
2026-01-20 17:03   ` David Howells
2026-01-21  4:45     ` Shyam Prasad N
2026-01-21  1:56   ` Steve French
2026-01-21  4:46     ` Shyam Prasad N
2026-01-21 23:36   ` David Howells
2026-01-21 23:50     ` David Howells
2026-01-29 11:38       ` Shyam Prasad N
2026-01-21 23:08 ` [PATCH 1/4] netfs: when subreq is marked for retry, do not check if it faced an error David Howells
2026-01-21 23:18 ` David Howells [this message]
2026-01-29 12:13   ` Shyam Prasad N
2026-01-29 13:43     ` David Howells

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=1652302.1769037531@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=bharathsm@microsoft.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=nspmangalore@gmail.com \
    --cc=pc@manguebit.com \
    --cc=smfrench@gmail.com \
    --cc=sprasad@microsoft.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