From: syzbot <syzbot+ef2c1c404cbcbcc66453@syzkaller.appspotmail.com>
To: asmadeus@codewreck.org, brauner@kernel.org,
ceph-devel@vger.kernel.org, dhowells@redhat.com,
ericvh@kernel.org, idryomov@gmail.com, jack@suse.cz,
jlayton@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux_oss@crudebyte.com,
lucho@ionkov.net, m@maowtm.org, mathieu.desnoyers@efficios.com,
mhiramat@kernel.org, netfs@lists.linux.dev, rostedt@goodmis.org,
syzkaller-bugs@googlegroups.com, v9fs@lists.linux.dev,
viro@zeniv.linux.org.uk, xiubli@redhat.com
Subject: Re: [syzbot] [nfs?] [netfs?] INFO: task hung in anon_pipe_write
Date: Tue, 04 Nov 2025 21:48:03 -0800 [thread overview]
Message-ID: <690ae513.050a0220.baf87.0009.GAE@google.com> (raw)
In-Reply-To: <68132c08.050a0220.14dd7d.0007.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=10be532f980000
start commit: 5bc1018675ec Merge tag 'pci-v6.15-fixes-3' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=9f5bd2a76d9d0b4e
dashboard link: https://syzkaller.appspot.com/bug?extid=ef2c1c404cbcbcc66453
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15631270580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12a0b0d4580000
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
prev parent reply other threads:[~2025-11-05 5:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 8:08 [syzbot] [netfs?] INFO: task hung in anon_pipe_write syzbot
2025-11-05 5:48 ` syzbot [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=690ae513.050a0220.baf87.0009.GAE@google.com \
--to=syzbot+ef2c1c404cbcbcc66453@syzkaller.appspotmail.com \
--cc=asmadeus@codewreck.org \
--cc=brauner@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=ericvh@kernel.org \
--cc=idryomov@gmail.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=m@maowtm.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=netfs@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=v9fs@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
--cc=xiubli@redhat.com \
/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.