From: syzbot <syzbot+234fdcc5f6633833a35c@syzkaller.appspotmail.com>
To: anna-maria@linutronix.de, bentiss@kernel.org,
chenl311@chinatelecom.cn, frederic@kernel.org, jikos@kernel.org,
jkosina@suse.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: Re: [syzbot] [kernel?] INFO: task hung in hidp_session_remove
Date: Sat, 20 Sep 2025 07:49:02 -0700 [thread overview]
Message-ID: <68cebede.a00a0220.37dadf.002d.GAE@google.com> (raw)
In-Reply-To: <688aa543.a00a0220.26d0e1.0030.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 4051ead99888f101be92c7ce90d2de09aac6fd1c
Author: Li Chen <chenl311@chinatelecom.cn>
Date: Fri Jun 20 12:02:31 2025 +0000
HID: rate-limit hid_warn to prevent log flooding
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1128a712580000
start commit: afd8c2c9e2e2 Merge branch 'ipv6-f6i-fib6_siblings-and-rt-f..
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=a4bcc0a11b3192be
dashboard link: https://syzkaller.appspot.com/bug?extid=234fdcc5f6633833a35c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15f458a2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1796c782580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: HID: rate-limit hid_warn to prevent log flooding
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-09-20 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 23:05 [syzbot] [kernel?] INFO: task hung in hidp_session_remove syzbot
2025-09-20 14:49 ` 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=68cebede.a00a0220.37dadf.002d.GAE@google.com \
--to=syzbot+234fdcc5f6633833a35c@syzkaller.appspotmail.com \
--cc=anna-maria@linutronix.de \
--cc=bentiss@kernel.org \
--cc=chenl311@chinatelecom.cn \
--cc=frederic@kernel.org \
--cc=jikos@kernel.org \
--cc=jkosina@suse.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 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.