From: syzbot <syzbot+0bab26cf3949891fb534@syzkaller.appspotmail.com>
To: andrii@kernel.org, anna-maria@linutronix.de, ast@kernel.org,
bpf@vger.kernel.org, daniel@iogearbox.net, frederic@kernel.org,
gregkh@linuxfoundation.org, hdanton@sina.com,
hverkuil+cisco@kernel.org, linux-kernel@vger.kernel.org,
penguin-kernel@I-love.SAKURA.ne.jp,
penguin-kernel@i-love.sakura.ne.jp, rafael@kernel.org,
sean@mess.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de
Subject: Re: [syzbot] [bpf?] INFO: rcu detected stall in watchdog
Date: Fri, 17 Oct 2025 15:57:03 -0700 [thread overview]
Message-ID: <68f2c9bf.050a0220.1186a4.051b.GAE@google.com> (raw)
In-Reply-To: <000000000000ae5aca05e68a7748@google.com>
syzbot suspects this issue was fixed by commit:
commit eecd203ada43a4693ce6fdd3a58ae10c7819252c
Author: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Date: Thu Jul 17 14:21:55 2025 +0000
media: imon: make send_packet() more robust
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=154d6734580000
start commit: e32cde8d2bd7 Merge tag 'sched_ext-for-6.12-rc1-fixes-1' of..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=286b31f2cf1c36b5
dashboard link: https://syzkaller.appspot.com/bug?extid=0bab26cf3949891fb534
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11646580580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: media: imon: make send_packet() more robust
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-10-17 22:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 21:14 [syzbot] INFO: rcu detected stall in watchdog syzbot
2025-10-17 22:57 ` syzbot [this message]
2025-10-18 5:28 ` [syzbot] [bpf?] " Tetsuo Handa
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=68f2c9bf.050a0220.1186a4.051b.GAE@google.com \
--to=syzbot+0bab26cf3949891fb534@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=frederic@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=hverkuil+cisco@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=rafael@kernel.org \
--cc=sean@mess.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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