public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+cf5f2dd02bbd4d2d411c@syzkaller.appspotmail.com>
To: bentiss@kernel.org, gregkh@linuxfoundation.org, jikos@kernel.org,
	 jkosina@suse.com, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org,  linux-usb@vger.kernel.org,
	lizhi.xu@windriver.com, rafael@kernel.org,
	 stuart.a.hayhurst@gmail.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] [input?] WARNING: ODEBUG bug in devres_release_group
Date: Tue, 11 Mar 2025 18:32:02 -0700	[thread overview]
Message-ID: <67d0e412.050a0220.14e108.0020.GAE@google.com> (raw)
In-Reply-To: <67923cb2.050a0220.2eae65.0006.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit 48e487b002891eb0aeaec704c9bed51f028deff1
Author: Stuart Hayhurst <stuart.a.hayhurst@gmail.com>
Date:   Tue Jan 21 20:00:07 2025 +0000

    HID: corsair-void: Add missing delayed work cancel for headset status

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=16abd478580000
start commit:   c4b9570cfb63 Merge tag 'audit-pr-20250121' of git://git.ke..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=5d46425e33fe266e
dashboard link: https://syzkaller.appspot.com/bug?extid=cf5f2dd02bbd4d2d411c
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1233c9f8580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=147eb618580000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: HID: corsair-void: Add missing delayed work cancel for headset status

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2025-03-12  1:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23 12:57 [syzbot] [input?] [usb?] WARNING: ODEBUG bug in devres_release_group syzbot
2025-01-24  8:09 ` [PATCH] HID: corsair-void: cancel delayed status work if device removed Lizhi Xu
2025-01-24  8:18   ` Greg KH
2025-01-24 13:00   ` Stuart
2025-03-12  1:32 ` 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=67d0e412.050a0220.14e108.0020.GAE@google.com \
    --to=syzbot+cf5f2dd02bbd4d2d411c@syzkaller.appspotmail.com \
    --cc=bentiss@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jikos@kernel.org \
    --cc=jkosina@suse.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lizhi.xu@windriver.com \
    --cc=rafael@kernel.org \
    --cc=stuart.a.hayhurst@gmail.com \
    --cc=syzkaller-bugs@googlegroups.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