From: David Howells <dhowells@redhat.com>
To: Lizhi Xu <lizhi.xu@windriver.com>
Cc: dhowells@redhat.com, asmadeus@codewreck.org, brauner@kernel.org,
ericvh@kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux_oss@crudebyte.com, lucho@ionkov.net,
syzbot+1fc6f64c40a9d143cfb6@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com, v9fs@lists.linux.dev
Subject: Re: [PATCH] netfs: If didn't read new data then abandon retry
Date: Fri, 13 Dec 2024 08:41:42 +0000 [thread overview]
Message-ID: <2890361.1734079302@warthog.procyon.org.uk> (raw)
In-Reply-To: <20241213072651.1475826-1-lizhi.xu@windriver.com>
Lizhi Xu <lizhi.xu@windriver.com> wrote:
> > (1) Replace NETFS_SREQ_NO_PROGRESS with NETFS_SREQ_MADE_PROGRESS and make
> > the filesystem set it if it managed to read or write at least one byte
> > of data. Clear this bit before issuing a subrequest.
> Will there be conflicts when reading and writing use the same flag to mark?
No, because, at the moment, a read done by a write (e.g. RMW with crypto) or a
write done by a read (e.g. writing just-read data to the cache) are handled
with an additional request structure since the set regions involved may differ
(RMW only needs read the unmodified ends for example).
David
prev parent reply other threads:[~2024-12-13 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 14:08 [syzbot] [mm?] BUG: stack guard page was hit in v9fs_file_read_iter syzbot
2024-11-08 3:40 ` [PATCH] netfs: If didn't read new data then abandon retry Lizhi Xu
2024-11-16 6:34 ` asmadeus
2024-12-09 15:53 ` David Howells
2024-12-13 7:26 ` Lizhi Xu
2024-12-13 8:41 ` David Howells [this message]
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=2890361.1734079302@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=asmadeus@codewreck.org \
--cc=brauner@kernel.org \
--cc=ericvh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux_oss@crudebyte.com \
--cc=lizhi.xu@windriver.com \
--cc=lucho@ionkov.net \
--cc=syzbot+1fc6f64c40a9d143cfb6@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=v9fs@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