All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+02b16343704b3af1667e@syzkaller.appspotmail.com>
To: andreyknvl@gmail.com, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in driver_unregister
Date: Sat, 28 May 2022 10:55:22 -0700	[thread overview]
Message-ID: <0000000000007a6b3605e01620c8@google.com> (raw)
In-Reply-To: <YpJaiGRcRjDzRxQC@rowland.harvard.edu>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+02b16343704b3af1667e@syzkaller.appspotmail.com

Tested on:

commit:         97fa5887 USB: new quirk for Dell Gen 2 devices
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
kernel config:  https://syzkaller.appspot.com/x/.config?x=d7b232ec3adf5c8d
dashboard link: https://syzkaller.appspot.com/bug?extid=02b16343704b3af1667e
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch:          https://syzkaller.appspot.com/x/patch.diff?x=10f44625f00000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2022-05-28 17:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27  9:25 [syzbot] WARNING in driver_unregister syzbot
2022-05-27 19:14 ` Alan Stern
2022-05-27 19:29   ` syzbot
2022-05-27 21:36     ` Alan Stern
2022-05-28 12:08       ` Greg KH
2022-05-28 14:45         ` Alan Stern
2022-05-28 15:02           ` syzbot
2022-05-28 16:26             ` Alan Stern
2022-05-28 17:02               ` syzbot
2022-05-28 17:23                 ` Alan Stern
2022-05-28 17:55                   ` syzbot [this message]
2022-05-28 20:22                     ` Alan Stern
2022-05-28 20:40                       ` syzbot
2022-05-29  0:56                       ` Hillf Danton
     [not found] <20220528023054.3646-1-hdanton@sina.com>
2022-05-28  2:53 ` syzbot

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=0000000000007a6b3605e01620c8@google.com \
    --to=syzbot+02b16343704b3af1667e@syzkaller.appspotmail.com \
    --cc=andreyknvl@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --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.