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 the handling of stream->front by removing it
Date: Wed, 25 Mar 2026 12:46:15 -0300 [thread overview]
Message-ID: <47ff638d0d81bdacc21cfd176d57415e@manguebit.org> (raw)
In-Reply-To: <4158599.1774426817@warthog.procyon.org.uk>
David Howells <dhowells@redhat.com> writes:
> The netfs_io_stream::front member is meant to point to the subrequest
> currently being collected on a stream, but it isn't actually used this way
> by direct write (which mostly ignores it). However, there's a tracepoint
> which looks at it. Further, stream->front is actually redundant with
> stream->subrequests.next.
>
> Fix the potential problem in the direct code by just removing the member
> and using stream->subrequests.next instead, thereby also simplifying the
> code.
>
> Fixes: a0b4c7a49137 ("netfs: Fix unbuffered/DIO writes to dispatch subrequests in strict sequence")
> Reported-by: Paulo Alcantara <pc@manguebit.org>
> Signed-off-by: David Howells <dhowells@redhat.com>
> cc: netfs@lists.linux.dev
> cc: linux-fsdevel@vger.kernel.org
> ---
> fs/netfs/buffered_read.c | 3 +--
> fs/netfs/direct_read.c | 3 +--
> fs/netfs/direct_write.c | 1 -
> fs/netfs/read_collect.c | 4 ++--
> fs/netfs/read_single.c | 1 -
> fs/netfs/write_collect.c | 4 ++--
> fs/netfs/write_issue.c | 3 +--
> include/linux/netfs.h | 1 -
> include/trace/events/netfs.h | 8 ++++----
> 9 files changed, 11 insertions(+), 17 deletions(-)
Reviewed-by: Paulo Alcantara (Red Hat) <pc@manguebit.org>
next prev parent reply other threads:[~2026-03-25 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 8:20 [PATCH] netfs: Fix the handling of stream->front by removing it David Howells
2026-03-25 15:46 ` Paulo Alcantara [this message]
2026-03-26 14:19 ` 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=47ff638d0d81bdacc21cfd176d57415e@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox