From: syzbot <syzbot+60df062e1c41940cae0f@syzkaller.appspotmail.com>
To: andriy.shevchenko@linux.intel.com,
dri-devel@lists.freedesktop.org, gregkh@linuxfoundation.org,
heikki.krogerus@linux.intel.com, linux-kernel@vger.kernel.org,
rafael.j.wysocki@intel.com, rafael@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in component_del
Date: Tue, 08 Feb 2022 02:37:10 -0800 [thread overview]
Message-ID: <000000000000a17f2305d77f4cb7@google.com> (raw)
In-Reply-To: <00000000000016f4ae05d5cec832@google.com>
syzbot has bisected this issue to:
commit 8c67d06f3fd9639c44d8147483fb1c132d71388f
Author: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Date: Thu Dec 23 08:23:49 2021 +0000
usb: Link the ports to the connectors they are attached to
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14063168700000
start commit: 555f3d7be91a Merge tag '5.17-rc3-ksmbd-server-fixes' of gi..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=16063168700000
console output: https://syzkaller.appspot.com/x/log.txt?x=12063168700000
kernel config: https://syzkaller.appspot.com/x/.config?x=266de9da75c71a45
dashboard link: https://syzkaller.appspot.com/bug?extid=60df062e1c41940cae0f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15880d84700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14de0c77b00000
Reported-by: syzbot+60df062e1c41940cae0f@syzkaller.appspotmail.com
Fixes: 8c67d06f3fd9 ("usb: Link the ports to the connectors they are attached to")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-02-08 11:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 22:36 [syzbot] WARNING in component_del syzbot
2022-02-08 7:51 ` syzbot
2022-02-08 12:30 ` Daniel Vetter
2022-02-08 12:39 ` Pavel Skripkin
2022-02-08 14:38 ` Fabio M. De Francesco
2022-02-08 14:51 ` syzbot
2022-02-08 10:37 ` syzbot [this message]
2022-02-09 13:42 ` Heikki Krogerus
2022-02-09 13:51 ` Pavel Skripkin
2022-02-09 13:56 ` Heikki Krogerus
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=000000000000a17f2305d77f4cb7@google.com \
--to=syzbot+60df062e1c41940cae0f@syzkaller.appspotmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox