From: Christian Schoenebeck <linux_oss@crudebyte.com>
To: Christian Brauner <brauner@kernel.org>,
David Howells <dhowells@redhat.com>,
Dominique Martinet <asmadeus@codewreck.org>
Cc: Eric Van Hensbergen <ericvh@kernel.org>,
Latchesar Ionkov <lucho@ionkov.net>,
Chris Arges <carges@cloudflare.com>,
Matthew Wilcox <willy@infradead.org>,
Steve French <sfrench@samba.org>,
v9fs@lists.linux.dev, netfs@lists.linux.dev,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] netfs: Fix early read unlock of page with EOF in middle
Date: Sun, 21 Dec 2025 00:50:09 +0100 [thread overview]
Message-ID: <22941732.EfDdHjke4D@weasel> (raw)
In-Reply-To: <8618918.T7Z3S40VBb@weasel>
On Saturday, 20 December 2025 15:55:09 CET Christian Schoenebeck wrote:
> On Saturday, 20 December 2025 13:31:40 CET David Howells wrote:
> > The read result collection for buffered reads seems to run ahead of the
> > completion of subrequests under some circumstances, as can be seen in the
[...]
> With the patch applied, this issue disappeared. Give me some hours for more
> thorough tests, due to the random factor involved.
Dominique, David, looks good! Thanks!
Tested-by: Christian Schoenebeck <linux_oss@crudebyte.com>
next prev parent reply other threads:[~2025-12-20 23:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-20 12:31 [PATCH] netfs: Fix early read unlock of page with EOF in middle David Howells
2025-12-20 14:55 ` Christian Schoenebeck
2025-12-20 15:17 ` David Howells
2025-12-20 23:50 ` Christian Schoenebeck [this message]
2025-12-20 23:54 ` Dominique Martinet
2025-12-24 12:31 ` 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=22941732.EfDdHjke4D@weasel \
--to=linux_oss@crudebyte.com \
--cc=asmadeus@codewreck.org \
--cc=brauner@kernel.org \
--cc=carges@cloudflare.com \
--cc=dhowells@redhat.com \
--cc=ericvh@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=netfs@lists.linux.dev \
--cc=sfrench@samba.org \
--cc=v9fs@lists.linux.dev \
--cc=willy@infradead.org \
/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.