From: syzbot <syzbot+d7f6a4fd149fcdaf780b@syzkaller.appspotmail.com>
To: andreyknvl@google.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
rafael@kernel.org, syzkaller-bugs@googlegroups.com
Subject: general protection fault in device_del (3)
Date: Wed, 15 May 2019 05:37:05 -0700 [thread overview]
Message-ID: <00000000000032a1d60588ec68dd@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 43151d6c usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=16a000a0a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=95aff7278e7ff25e
dashboard link: https://syzkaller.appspot.com/bug?extid=d7f6a4fd149fcdaf780b
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17605e22a00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1045a49ca00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+d7f6a4fd149fcdaf780b@syzkaller.appspotmail.com
usb 1-1: string descriptor 0 read error: -71
usb 1-1: claimed gadget: Vendor=0424 ProdID=c001 Bus=01 Device=02
usb 1-1: device path: /sys/bus/usb/devices/1-1:0.133
most_core: registered new device mdev0 (usb_device 1-1:0.133)
usb 1-1: USB disconnect, device number 2
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] SMP KASAN PTI
CPU: 1 PID: 17 Comm: kworker/1:0 Not tainted 5.1.0-rc3+ #8
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: usb_hub_wq hub_event
RIP: 0010:device_del+0x76/0xb90 drivers/base/core.c:2224
Code: f1 f1 f1 f1 c7 40 04 00 07 f3 f3 65 48 8b 04 25 28 00 00 00 48 89 84
24 88 00 00 00 31 c0 e8 c1 ce d7 fe 48 89 d8 48 c1 e8 03 <80> 3c 28 00 0f
85 82 0a 00 00 48 8b 03 4c 8d 63 60 31 f6 4c 8d 7b
RSP: 0018:ffff8881d9e4f7c0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8264999f RDI: 0000000000000000
RBP: dffffc0000000000 R08: ffff8881d9e33000 R09: ffffed1039951b26
R10: ffffed1039951b25 R11: ffff8881cca8d92f R12: ffff8881cde8f828
R13: ffff8881cca8d860 R14: ffff8881cde8f730 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8881db300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f77df136000 CR3: 00000001cf00a000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
device_unregister+0x11/0x30 drivers/base/core.c:2301
hdm_disconnect+0xdf/0x200 drivers/staging/most/usb/usb.c:1208
usb_unbind_interface+0x1c4/0x8b0 drivers/usb/core/driver.c:423
__device_release_driver drivers/base/dd.c:1082 [inline]
device_release_driver_internal+0x431/0x4f0 drivers/base/dd.c:1113
bus_remove_device+0x2ee/0x4c0 drivers/base/bus.c:556
device_del+0x462/0xb90 drivers/base/core.c:2269
usb_disable_device+0x211/0x690 drivers/usb/core/message.c:1237
usb_disconnect+0x284/0x840 drivers/usb/core/hub.c:2197
hub_port_connect drivers/usb/core/hub.c:4940 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5204 [inline]
port_event drivers/usb/core/hub.c:5350 [inline]
hub_event+0x13f8/0x35a0 drivers/usb/core/hub.c:5432
process_one_work+0x90a/0x1580 kernel/workqueue.c:2269
process_scheduled_works kernel/workqueue.c:2331 [inline]
worker_thread+0x7ab/0xe20 kernel/workqueue.c:2417
kthread+0x30e/0x420 kernel/kthread.c:253
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352
Modules linked in:
---[ end trace d819a3b977ff54ad ]---
RIP: 0010:device_del+0x76/0xb90 drivers/base/core.c:2224
Code: f1 f1 f1 f1 c7 40 04 00 07 f3 f3 65 48 8b 04 25 28 00 00 00 48 89 84
24 88 00 00 00 31 c0 e8 c1 ce d7 fe 48 89 d8 48 c1 e8 03 <80> 3c 28 00 0f
85 82 0a 00 00 48 8b 03 4c 8d 63 60 31 f6 4c 8d 7b
RSP: 0018:ffff8881d9e4f7c0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8264999f RDI: 0000000000000000
RBP: dffffc0000000000 R08: ffff8881d9e33000 R09: ffffed1039951b26
R10: ffffed1039951b25 R11: ffff8881cca8d92f R12: ffff8881cde8f828
R13: ffff8881cca8d860 R14: ffff8881cde8f730 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8881db300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f77df136000 CR3: 00000001cf00a000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2019-05-15 12:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 12:37 syzbot [this message]
2019-11-19 13:43 ` general protection fault in device_del (3) Andrey Konovalov
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=00000000000032a1d60588ec68dd@google.com \
--to=syzbot+d7f6a4fd149fcdaf780b@syzkaller.appspotmail.com \
--cc=andreyknvl@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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.