All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+8fe2d362af0e1cba8735@syzkaller.appspotmail.com>
To: agordeev@linux.ibm.com, akrowiak@linux.ibm.com,
	anna-maria@linutronix.de,  benjamin.tissoires@redhat.com,
	chenl311@chinatelecom.cn, clg@redhat.com,  davem@davemloft.net,
	david.rheinsberg@gmail.com, edumazet@google.com,
	 frederic@kernel.org, jikos@kernel.org, jkosina@suse.com,
	kuba@kernel.org,  linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org,  mjrosato@linux.ibm.com,
	netdev@vger.kernel.org, pabeni@redhat.com,
	 syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: Re: [syzbot] [kernel?] INFO: task hung in uhid_char_release
Date: Sat, 20 Sep 2025 20:29:02 -0700	[thread overview]
Message-ID: <68cf70fe.a00a0220.37dadf.0036.GAE@google.com> (raw)
In-Reply-To: <000000000000c329d505fed78c74@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=12071534580000
start commit:   fb4d33ab452e Merge tag '6.16-rc2-ksmbd-server-fixes' of gi..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=6a237c32900fc479
dashboard link: https://syzkaller.appspot.com/bug?extid=8fe2d362af0e1cba8735
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=13d7ed0c580000

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

      parent reply	other threads:[~2025-09-21  3:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24  3:16 [syzbot] [input?] INFO: task hung in uhid_char_release syzbot
2023-08-29 17:28 ` syzbot
2023-08-29 18:56   ` Matthew Rosato
2025-09-21  3:29 ` 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=68cf70fe.a00a0220.37dadf.0036.GAE@google.com \
    --to=syzbot+8fe2d362af0e1cba8735@syzkaller.appspotmail.com \
    --cc=agordeev@linux.ibm.com \
    --cc=akrowiak@linux.ibm.com \
    --cc=anna-maria@linutronix.de \
    --cc=benjamin.tissoires@redhat.com \
    --cc=chenl311@chinatelecom.cn \
    --cc=clg@redhat.com \
    --cc=davem@davemloft.net \
    --cc=david.rheinsberg@gmail.com \
    --cc=edumazet@google.com \
    --cc=frederic@kernel.org \
    --cc=jikos@kernel.org \
    --cc=jkosina@suse.com \
    --cc=kuba@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjrosato@linux.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --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.