All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+617f4ccb03b9869f6494@syzkaller.appspotmail.com>
To: dmitry.torokhov@gmail.com, eadavis@qq.com,
	gregkh@linuxfoundation.org,  jandryuk@gmail.com,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-usb@vger.kernel.org, peter.hutterer@who-t.net,
	rafael@kernel.org,  syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [input?] [usb?] WARNING in input_unregister_device (2)
Date: Mon, 22 Jul 2024 22:33:03 -0700	[thread overview]
Message-ID: <000000000000dbdb25061de37eda@google.com> (raw)
In-Reply-To: <0000000000004b841a060e876595@google.com>

syzbot suspects this issue was fixed by commit:

commit 0774d19038c496f0c3602fb505c43e1b2d8eed85
Author: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date:   Mon Apr 29 21:50:41 2024 +0000

    Input: try trimming too long modalias strings

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=11c0adc3980000
start commit:   1c892cdd8fe0 Merge tag 'vfs-6.8-rc6.fixes' of git://git.ke..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=eff9f3183d0a20dd
dashboard link: https://syzkaller.appspot.com/bug?extid=617f4ccb03b9869f6494
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17985b34180000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16d8d43c180000

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

#syz fix: Input: try trimming too long modalias strings

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

      parent reply	other threads:[~2024-07-23  5:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-09 18:22 [syzbot] [kernel?] WARNING in input_unregister_device (2) syzbot
2024-02-17 12:01 ` [syzbot] [usb?] [input?] " syzbot
2024-02-24  1:21   ` Edward Adam Davis
2024-02-24  2:30     ` syzbot
2024-07-23  5:33 ` 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=000000000000dbdb25061de37eda@google.com \
    --to=syzbot+617f4ccb03b9869f6494@syzkaller.appspotmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=eadavis@qq.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jandryuk@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=peter.hutterer@who-t.net \
    --cc=rafael@kernel.org \
    --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 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.