From: syzbot <syzbot+666a9cb4c41986207cdf@syzkaller.appspotmail.com>
To: asmadeus@codewreck.org, dhowells@redhat.com, ericvh@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux_oss@crudebyte.com, lucho@ionkov.net, m@maowtm.org,
netfs@lists.linux.dev, pc@manguebit.org,
syzkaller-bugs@googlegroups.com, v9fs@lists.linux.dev
Subject: Re: [syzbot] [netfs?] INFO: task hung in netfs_retry_writes
Date: Thu, 13 Nov 2025 01:33:04 -0800 [thread overview]
Message-ID: <6915a5d0.050a0220.3565dc.0023.GAE@google.com> (raw)
In-Reply-To: <67886ff3.050a0220.20d369.0021.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 290434474c332a2ba9c8499fe699c7f2e1153280
Author: Tingmao Wang <m@maowtm.org>
Date: Sun Apr 6 16:18:42 2025 +0000
fs/9p: Refresh metadata in d_revalidate for uncached mode too
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15831c12580000
start commit: a2e94e80790b Merge tag 'block-6.17-20250822' of git://git...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=d4703ac89d9e185a
dashboard link: https://syzkaller.appspot.com/bug?extid=666a9cb4c41986207cdf
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=137d5062580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15e33fa2580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs/9p: Refresh metadata in d_revalidate for uncached mode too
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2025-11-13 9:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <67886ff3.050a0220.20d369.0021.GAE@google.com>]
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=6915a5d0.050a0220.3565dc.0023.GAE@google.com \
--to=syzbot+666a9cb4c41986207cdf@syzkaller.appspotmail.com \
--cc=asmadeus@codewreck.org \
--cc=dhowells@redhat.com \
--cc=ericvh@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=m@maowtm.org \
--cc=netfs@lists.linux.dev \
--cc=pc@manguebit.org \
--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