All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@manguebit.org>
To: David Howells <dhowells@redhat.com>,
	Christian Brauner <brauner@kernel.org>
Cc: dhowells@redhat.com, netfs@lists.linux.dev,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] netfs: Fix barriering when walking subrequest list
Date: Thu, 02 Jul 2026 09:59:36 -0300	[thread overview]
Message-ID: <4941c0d1bb3092af2a379de75fbe2908@manguebit.org> (raw)
In-Reply-To: <138807.1782980582@warthog.procyon.org.uk>

David Howells <dhowells@redhat.com> writes:

> Fix the barriering used when walking the subrequest list in retry as
> there's a possibility of seeing a subreq that's just been added by the
> application thread.
>
> Fixes: ee4cdf7ba857 ("netfs: Speed up buffered reading")
> Fixes: 288ace2f57c9 ("netfs: New writeback implementation")
> Link: https://sashiko.dev/#/patchset/20260608145432.681865-1-dhowells%40redhat.com
> Signed-off-by: David Howells <dhowells@redhat.com>
> cc: Paulo Alcantara <pc@manguebit.org>
> cc: netfs@lists.linux.dev
> cc: linux-fsdevel@vger.kernel.org
> ---
>  fs/netfs/read_retry.c  |    7 ++++++-
>  fs/netfs/write_retry.c |    7 ++++++-
>  2 files changed, 12 insertions(+), 2 deletions(-)

Reviewed-by: Paulo Alcantara (Red Hat) <pc@manguebit.org>

  reply	other threads:[~2026-07-02 12:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02  8:23 [PATCH] netfs: Fix barriering when walking subrequest list David Howells
2026-07-02 12:59 ` Paulo Alcantara [this message]
2026-07-03  9:52 ` Christian Brauner

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=4941c0d1bb3092af2a379de75fbe2908@manguebit.org \
    --to=pc@manguebit.org \
    --cc=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfs@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.