From: syzbot <syzbot+5984e31a805252b3b40a@syzkaller.appspotmail.com>
To: asmadeus@codewreck.org, brauner@kernel.org,
ceph-devel@vger.kernel.org, dhowells@redhat.com,
gregkh@linuxfoundation.org, idryomov@gmail.com, jack@suse.cz,
jlayton@kernel.org, kprateek.nayak@amd.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, mhiramat@kernel.org,
netfs@lists.linux.dev, oleg@redhat.com, rostedt@goodmis.org,
syzkaller-bugs@googlegroups.com, tj@kernel.org,
viro@zeniv.linux.org.uk, xiubli@redhat.com
Subject: Re: [syzbot] [kernfs?] [netfs?] INFO: task hung in pipe_write (6)
Date: Sun, 02 Nov 2025 09:38:02 -0800 [thread overview]
Message-ID: <690796fa.a70a0220.37351b.000b.GAE@google.com> (raw)
In-Reply-To: <67b454d4.050a0220.173698.0051.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit e8fe3f07a357c39d429e02ca34f740692d88967a
Author: Oleg Nesterov <oleg@redhat.com>
Date: Tue Aug 19 16:10:13 2025 +0000
9p/trans_fd: p9_fd_request: kick rx thread if EPOLLIN
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=154ba342580000
start commit: ad1b832bf1cf Merge tag 'devicetree-fixes-for-6.14-1' of gi..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=e55cabe422b4fcaf
dashboard link: https://syzkaller.appspot.com/bug?extid=5984e31a805252b3b40a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=170d57df980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12df35a4580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: 9p/trans_fd: p9_fd_request: kick rx thread if EPOLLIN
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-11-02 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 9:37 [syzbot] [netfs?] INFO: task hung in pipe_write (6) syzbot
2025-11-02 17:38 ` 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=690796fa.a70a0220.37351b.000b.GAE@google.com \
--to=syzbot+5984e31a805252b3b40a@syzkaller.appspotmail.com \
--cc=asmadeus@codewreck.org \
--cc=brauner@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=idryomov@gmail.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=kprateek.nayak@amd.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=netfs@lists.linux.dev \
--cc=oleg@redhat.com \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox