Re: WARNING in __uwb_rc_neh_rm

From: Andrey Konovalov <andreyknvl@google.com>
To: syzbot <syzbot+c44bb3aca1a5e07c76df@syzkaller.appspotmail.com>
Cc: alexios.zavras@intel.com, Allison Randal <allison@lohutok.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	USB list <linux-usb@vger.kernel.org>,
	Richard Fontana <rfontana@redhat.com>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: WARNING in __uwb_rc_neh_rm
Date: Thu, 18 Jun 2020 14:07:21 +0200	[thread overview]
Message-ID: <CAAeHK+xaACXn+CGCGiG+DcGkjuN0m2w3T7aMYvQz+zRr+R_-NQ@mail.gmail.com> (raw)
In-Reply-To: <000000000000448f5a058e804752@google.com>

On Thu, Jul 25, 2019 at 2:08 PM syzbot
<syzbot+c44bb3aca1a5e07c76df@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:    6a3599ce 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=17eb58cc600000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=700ca426ab83faae
> dashboard link: https://syzkaller.appspot.com/bug?extid=c44bb3aca1a5e07c76df
> compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14ebb65c600000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17d95382600000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+c44bb3aca1a5e07c76df@syzkaller.appspotmail.com
>
> ------------[ cut here ]------------
> list_del corruption, ffff8881d0a03130->next is LIST_POISON1
> (dead000000000100)
> WARNING: CPU: 0 PID: 5 at lib/list_debug.c:45
> __list_del_entry_valid+0xd3/0x170 lib/list_debug.c:45
> Kernel panic - not syncing: panic_on_warn set ...
> CPU: 0 PID: 5 Comm: kworker/0:0 Not tainted 5.2.0-rc6+ #15
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> Workqueue: usb_hub_wq hub_event
> Call Trace:
>   __dump_stack lib/dump_stack.c:77 [inline]
>   dump_stack+0xca/0x13e lib/dump_stack.c:113
>   panic+0x292/0x6c9 kernel/panic.c:219
>   __warn.cold+0x20/0x4b kernel/panic.c:576
>   report_bug+0x262/0x2a0 lib/bug.c:186
>   fixup_bug arch/x86/kernel/traps.c:179 [inline]
>   fixup_bug arch/x86/kernel/traps.c:174 [inline]
>   do_error_trap+0x12b/0x1e0 arch/x86/kernel/traps.c:272
>   do_invalid_op+0x32/0x40 arch/x86/kernel/traps.c:291
>   invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:986
> RIP: 0010:__list_del_entry_valid+0xd3/0x170 lib/list_debug.c:45
> Code: 93 00 00 00 49 8b 55 08 48 39 f2 75 51 b8 01 00 00 00 48 83 c4 08 41
> 5c 41 5d c3 4c 89 ea 48 c7 c7 40 0b ba 85 e8 c8 d1 33 ff <0f> 0b 48 83 c4
> 08 31 c0 41 5c 41 5d c3 4c 89 e2 48 c7 c7 a0 0b ba
> RSP: 0018:ffff8881d9dc6d80 EFLAGS: 00010086
> RAX: 0000000000000000 RBX: ffff8881d0a030c0 RCX: 0000000000000000
> RDX: 0000000000000000 RSI: ffffffff8127ef3d RDI: ffffed103b3b8da2
> RBP: 0000000000000000 R08: ffff8881d9d8e000 R09: 0000000000000008
> R10: fffffbfff0d5dc9c R11: ffffffff86aee4e3 R12: dead000000000200
> R13: dead000000000100 R14: ffff8881d3eab830 R15: 00000000ffffffb9
>   __list_del_entry include/linux/list.h:117 [inline]
>   list_del include/linux/list.h:125 [inline]
>   __uwb_rc_neh_rm+0xc5/0x220 drivers/uwb/neh.c:243
>   uwb_rc_neh_rm+0x30/0x60 drivers/uwb/neh.c:259
>   uwb_rc_cmd_async+0x29a/0x310 drivers/uwb/reset.c:93
>   __uwb_rc_cmd+0x10f/0x1e0 drivers/uwb/reset.c:171
>   uwb_rc_cmd+0xc2/0x130 drivers/uwb/reset.c:220
>   uwb_rc_reset+0x15e/0x218 drivers/uwb/reset.c:292
>   uwb_rc_setup+0x84/0x320 drivers/uwb/lc-rc.c:282
>   uwb_rc_add+0x246/0x42f drivers/uwb/lc-rc.c:351
>   hwarc_probe+0x3ce/0x980 drivers/uwb/hwa-rc.c:843
>   usb_probe_interface+0x305/0x7a0 drivers/usb/core/driver.c:361
>   really_probe+0x281/0x660 drivers/base/dd.c:509
>   driver_probe_device+0x104/0x210 drivers/base/dd.c:670
>   __device_attach_driver+0x1c2/0x220 drivers/base/dd.c:777
>   bus_for_each_drv+0x15c/0x1e0 drivers/base/bus.c:454
>   __device_attach+0x217/0x360 drivers/base/dd.c:843
>   bus_probe_device+0x1e4/0x290 drivers/base/bus.c:514
>   device_add+0xae6/0x16f0 drivers/base/core.c:2111
>   usb_set_configuration+0xdf6/0x1670 drivers/usb/core/message.c:2023
>   generic_probe+0x9d/0xd5 drivers/usb/core/generic.c:210
>   usb_probe_device+0x99/0x100 drivers/usb/core/driver.c:266
>   really_probe+0x281/0x660 drivers/base/dd.c:509
>   driver_probe_device+0x104/0x210 drivers/base/dd.c:670
>   __device_attach_driver+0x1c2/0x220 drivers/base/dd.c:777
>   bus_for_each_drv+0x15c/0x1e0 drivers/base/bus.c:454
>   __device_attach+0x217/0x360 drivers/base/dd.c:843
>   bus_probe_device+0x1e4/0x290 drivers/base/bus.c:514
>   device_add+0xae6/0x16f0 drivers/base/core.c:2111
>   usb_new_device.cold+0x6a4/0xe61 drivers/usb/core/hub.c:2536
>   hub_port_connect drivers/usb/core/hub.c:5098 [inline]
>   hub_port_connect_change drivers/usb/core/hub.c:5213 [inline]
>   port_event drivers/usb/core/hub.c:5359 [inline]
>   hub_event+0x1abd/0x3550 drivers/usb/core/hub.c:5441
>   process_one_work+0x905/0x1570 kernel/workqueue.c:2269
>   worker_thread+0x96/0xe20 kernel/workqueue.c:2415
>   kthread+0x30b/0x410 kernel/kthread.c:255
>   ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352
> Kernel Offset: disabled
> Rebooting in 86400 seconds..
>
>
> ---
> 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

Closing old USB bugs that haven't happened for a long time.

#syz invalid