From: syzbot <syzbot+879882be5b42e60d4d98@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, fweisbec@gmail.com,
hdanton@sina.com, hpa@zytor.com, hverkuil+cisco@kernel.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, mingo@kernel.org, mingo@redhat.com,
pbonzini@redhat.com, penguin-kernel@I-love.SAKURA.ne.jp,
penguin-kernel@i-love.sakura.ne.jp, sean@mess.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
vkuznets@redhat.com, wanpengli@tencent.com, x86@kernel.org
Subject: Re: [syzbot] [usb?] INFO: rcu detected stall in dummy_timer (4)
Date: Mon, 13 Oct 2025 10:22:02 -0700 [thread overview]
Message-ID: <68ed353a.050a0220.ac43.003c.GAE@google.com> (raw)
In-Reply-To: <0000000000004d1b5605e3573f8e@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=15729dcd980000
start commit: 200e340f2196 Merge tag 'pull-work.dcache' of git://git.ker..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=f2886ebe3c7b3459
dashboard link: https://syzkaller.appspot.com/bug?extid=879882be5b42e60d4d98
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=156ff9f2080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=178a89f2080000
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-13 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 3:52 [syzbot] INFO: rcu detected stall in dummy_timer (4) syzbot
2025-10-13 17:22 ` syzbot [this message]
2025-10-14 10:23 ` [syzbot] [usb?] " 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=68ed353a.050a0220.ac43.003c.GAE@google.com \
--to=syzbot+879882be5b42e60d4d98@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fweisbec@gmail.com \
--cc=hdanton@sina.com \
--cc=hpa@zytor.com \
--cc=hverkuil+cisco@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=sean@mess.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/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.