INFO: task hung in usbdev_release

13 views
Skip to first unread message

syzbot

unread,
Oct 24, 2020, 6:17:25 PM10/24/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: ad326970 Linux 4.19.152
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11c1fc18500000
kernel config: https://syzkaller.appspot.com/x/.config?x=1ec7667b405157e
dashboard link: https://syzkaller.appspot.com/bug?extid=df12dacc8c0f1b1db1f6
compiler: gcc (GCC) 10.1.0-syz 20200507

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+df12da...@syzkaller.appspotmail.com

vhci_hcd: vhci_device speed not set
sp0: Synchronizing with TNC
usb 9-1: new full-speed USB device number 2 using vhci_hcd
sp0: Synchronizing with TNC
Bluetooth: hci5: command 0x0406 tx timeout
INFO: task syz-executor.0:20203 blocked for more than 140 seconds.
Not tainted 4.19.152-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.0 D28648 20203 8115 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2828 [inline]
__schedule+0x887/0x2040 kernel/sched/core.c:3517
schedule+0x8d/0x1b0 kernel/sched/core.c:3561
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:3619
__mutex_lock_common kernel/locking/mutex.c:1002 [inline]
__mutex_lock+0x647/0x1260 kernel/locking/mutex.c:1072
device_lock include/linux/device.h:1173 [inline]
usbdev_release+0x83/0x410 drivers/usb/core/devio.c:1049
__fput+0x2ce/0x890 fs/file_table.c:278
task_work_run+0x148/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x251/0x2a0 arch/x86/entry/common.c:167
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4177b1
Code: 00 31 c0 48 8b 4c 24 28 e9 b3 fe ff ff 31 f6 e9 53 fe ff ff 48 8b 5a 20 eb 03 48 8b 1b 48 85 db 74 29 8d 41 fe 39 43 58 0f 85 <5d> 01 00 00 8d 71 ff f0 0f b1 73 58 40 0f 94 c6 40 84 f6 0f 85 aa
RSP: 002b:00007ffe95a024f0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000005 RCX: 00000000004177b1
RDX: 0000000000000000 RSI: 000000000000165f RDI: 0000000000000004
RBP: 0000000000000001 R08: 00000000b872965f R09: 00000000b8729663
R10: 00007ffe95a025d0 R11: 0000000000000293 R12: 000000000118c9a0
R13: 000000000118c9a0 R14: 00000000000003e8 R15: 000000000118bfd4
INFO: task syz-executor.1:20240 blocked for more than 140 seconds.
Not tainted 4.19.152-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.1 D28856 20240 8117 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2828 [inline]
__schedule+0x887/0x2040 kernel/sched/core.c:3517
schedule+0x8d/0x1b0 kernel/sched/core.c:3561
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:3619
__mutex_lock_common kernel/locking/mutex.c:1002 [inline]
__mutex_lock+0x647/0x1260 kernel/locking/mutex.c:1072
device_lock include/linux/device.h:1173 [inline]
usbdev_open+0x152/0x7f0 drivers/usb/core/devio.c:1007
chrdev_open+0x266/0x770 fs/char_dev.c:423
do_dentry_open+0x4aa/0x1160 fs/open.c:796
do_last fs/namei.c:3421 [inline]
path_openat+0x793/0x2df0 fs/namei.c:3537
do_filp_open+0x18c/0x3f0 fs/namei.c:3567
do_sys_open+0x3b3/0x520 fs/open.c:1085
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x417951
Code: Bad RIP value.
RSP: 002b:00007ff59e55e820 EFLAGS: 00000293 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 6666666666666667 RCX: 0000000000417951
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 00007ff59e55e850
RBP: 000000000118bf60 R08: 000000000000000f R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000293 R12: 000000000118bf2c
R13: 00007fff3284973f R14: 00007ff59e55f9c0 R15: 000000000118bf2c
INFO: task syz-executor.4:20245 blocked for more than 140 seconds.
Not tainted 4.19.152-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.4 D29496 20245 8123 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2828 [inline]
__schedule+0x887/0x2040 kernel/sched/core.c:3517
schedule+0x8d/0x1b0 kernel/sched/core.c:3561
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:3619
__mutex_lock_common kernel/locking/mutex.c:1002 [inline]
__mutex_lock+0x647/0x1260 kernel/locking/mutex.c:1072
device_lock include/linux/device.h:1173 [inline]
usbdev_open+0x152/0x7f0 drivers/usb/core/devio.c:1007
chrdev_open+0x266/0x770 fs/char_dev.c:423
do_dentry_open+0x4aa/0x1160 fs/open.c:796
do_last fs/namei.c:3421 [inline]
path_openat+0x793/0x2df0 fs/namei.c:3537
do_filp_open+0x18c/0x3f0 fs/namei.c:3567
do_sys_open+0x3b3/0x520 fs/open.c:1085
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x417951
Code: Bad RIP value.
RSP: 002b:00007fa2e41f7820 EFLAGS: 00000293 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 6666666666666667 RCX: 0000000000417951
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 00007fa2e41f7850
RBP: 000000000118bf60 R08: 000000000000000f R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000293 R12: 000000000118bf2c
R13: 00007ffe5314bfff R14: 00007fa2e41f89c0 R15: 000000000118bf2c
INFO: task syz-executor.3:20248 blocked for more than 140 seconds.
Not tainted 4.19.152-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.3 D27640 20248 8121 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2828 [inline]
__schedule+0x887/0x2040 kernel/sched/core.c:3517
schedule+0x8d/0x1b0 kernel/sched/core.c:3561
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:3619
__mutex_lock_common kernel/locking/mutex.c:1002 [inline]
__mutex_lock+0x647/0x1260 kernel/locking/mutex.c:1072
device_lock include/linux/device.h:1173 [inline]
usbdev_open+0x152/0x7f0 drivers/usb/core/devio.c:1007
chrdev_open+0x266/0x770 fs/char_dev.c:423
do_dentry_open+0x4aa/0x1160 fs/open.c:796
do_last fs/namei.c:3421 [inline]
path_openat+0x793/0x2df0 fs/namei.c:3537
do_filp_open+0x18c/0x3f0 fs/namei.c:3567
do_sys_open+0x3b3/0x520 fs/open.c:1085
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x417951
Code: Bad RIP value.
RSP: 002b:00007fc5e149e820 EFLAGS: 00000293 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 6666666666666667 RCX: 0000000000417951
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 00007fc5e149e850
RBP: 000000000118bf60 R08: 000000000000000f R09: 0000000000000000
R10: 0000000000000003 R11: 0000000000000293 R12: 000000000118bf2c
R13: 00007ffeb90ad83f R14: 00007fc5e149f9c0 R15: 000000000118bf2c

Showing all locks held in the system:
1 lock held by khungtaskd/1566:
#0: 00000000eaf71a7f (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4440
5 locks held by kworker/1:4/9347:
#0: 00000000a4eae4ef ((wq_completion)"usb_hub_wq"){+.+.}, at: process_one_work+0x767/0x1570 kernel/workqueue.c:2126
#1: 000000008ec8838f ((work_completion)(&hub->events)){+.+.}, at: process_one_work+0x79c/0x1570 kernel/workqueue.c:2130
#2: 0000000047321a21 (&dev->mutex){....}, at: device_lock include/linux/device.h:1173 [inline]
#2: 0000000047321a21 (&dev->mutex){....}, at: hub_event+0x11b/0x43f0 drivers/usb/core/hub.c:5337
#3: 0000000029ad8d48 (&port_dev->status_lock){+.+.}, at: usb_lock_port drivers/usb/core/hub.c:2977 [inline]
#3: 0000000029ad8d48 (&port_dev->status_lock){+.+.}, at: hub_port_connect drivers/usb/core/hub.c:5019 [inline]
#3: 0000000029ad8d48 (&port_dev->status_lock){+.+.}, at: hub_port_connect_change drivers/usb/core/hub.c:5203 [inline]
#3: 0000000029ad8d48 (&port_dev->status_lock){+.+.}, at: port_event drivers/usb/core/hub.c:5311 [inline]
#3: 0000000029ad8d48 (&port_dev->status_lock){+.+.}, at: hub_event+0x1ce3/0x43f0 drivers/usb/core/hub.c:5391
#4: 000000004f1a0a9e (hcd->address0_mutex){+.+.}, at: hub_port_init+0x1b6/0x2fa0 drivers/usb/core/hub.c:4528
1 lock held by syz-executor.0/20203:
#0: 0000000047321a21 (&dev->mutex){....}, at: device_lock include/linux/device.h:1173 [inline]
#0: 0000000047321a21 (&dev->mutex){....}, at: usbdev_release+0x83/0x410 drivers/usb/core/devio.c:1049
1 lock held by syz-executor.1/20240:
#0: 0000000047321a21 (&dev->mutex){....}, at: device_lock include/linux/device.h:1173 [inline]
#0: 0000000047321a21 (&dev->mutex){....}, at: usbdev_open+0x152/0x7f0 drivers/usb/core/devio.c:1007
1 lock held by syz-executor.4/20245:
#0: 0000000047321a21 (&dev->mutex){....}, at: device_lock include/linux/device.h:1173 [inline]
#0: 0000000047321a21 (&dev->mutex){....}, at: usbdev_open+0x152/0x7f0 drivers/usb/core/devio.c:1007
1 lock held by syz-executor.3/20248:
#0: 0000000047321a21 (&dev->mutex){....}, at: device_lock include/linux/device.h:1173 [inline]
#0: 0000000047321a21 (&dev->mutex){....}, at: usbdev_open+0x152/0x7f0 drivers/usb/core/devio.c:1007

=============================================

NMI backtrace for cpu 0
CPU: 0 PID: 1566 Comm: khungtaskd Not tainted 4.19.152-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
nmi_cpu_backtrace.cold+0x63/0xa2 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x1a6/0x1eb lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:203 [inline]
watchdog+0x991/0xe60 kernel/hung_task.c:287
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 10 Comm: rcu_preempt Not tainted 4.19.152-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:rcu_read_unlock_sched_notrace include/linux/rcupdate.h:771 [inline]
RIP: 0010:trace_timer_cancel include/trace/events/timer.h:132 [inline]
RIP: 0010:debug_deactivate kernel/time/timer.c:780 [inline]
RIP: 0010:detach_timer kernel/time/timer.c:824 [inline]
RIP: 0010:detach_if_pending+0x34d/0x460 kernel/time/timer.c:843
Code: ff 31 ff 89 c5 89 c6 e8 11 23 0f 00 85 ed 74 1a e8 98 21 0f 00 0f b6 2d 30 be b8 09 31 ff 89 ee e8 b8 22 0f 00 40 84 ed 74 45 <e8> 7e 21 0f 00 65 ff 0d d7 33 ac 7e 40 0f 94 c5 31 ff 89 ee e8 9a
RSP: 0018:ffff8880b5a77b68 EFLAGS: 00000002
RAX: 0000000000000000 RBX: ffff8880b5a77cc0 RCX: ffffffff8155ab87
RDX: 0000000000000001 RSI: ffff8880b5a62280 RDI: 0000000000000005
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff8880ba122d38
R13: 0000000000000001 R14: ffff8880b5a77cc8 R15: 00000000ffffffff
FS: 0000000000000000(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fecdaea3000 CR3: 00000000a16dd000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
try_to_del_timer_sync+0xaa/0x110 kernel/time/timer.c:1240
del_timer_sync+0x1a4/0x270 kernel/time/timer.c:1305
schedule_timeout+0x4d7/0xfe0 kernel/time/timer.c:1826
rcu_gp_kthread+0xdad/0x21c0 kernel/rcu/tree.c:2202
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415


---
This report 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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Oct 26, 2020, 2:21:17 AM10/26/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 5b7a52cd Linux 4.14.202
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13761850500000
kernel config: https://syzkaller.appspot.com/x/.config?x=fa386e02ca459165
dashboard link: https://syzkaller.appspot.com/bug?extid=3eb3ce4b14f240e2cedd
compiler: gcc (GCC) 10.1.0-syz 20200507

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3eb3ce...@syzkaller.appspotmail.com

INFO: task syz-executor.2:17202 blocked for more than 140 seconds.
Not tainted 4.14.202-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.2 D26960 17202 8030 0x80000002
Call Trace:
context_switch kernel/sched/core.c:2808 [inline]
__schedule+0x88b/0x1de0 kernel/sched/core.c:3384
schedule+0x8d/0x1b0 kernel/sched/core.c:3428
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:3486
__mutex_lock_common kernel/locking/mutex.c:833 [inline]
__mutex_lock+0x669/0x1310 kernel/locking/mutex.c:893
device_lock include/linux/device.h:1081 [inline]
usbdev_release+0x73/0x380 drivers/usb/core/devio.c:1066
__fput+0x25f/0x7a0 fs/file_table.c:210
task_work_run+0x11f/0x190 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xa08/0x27f0 kernel/exit.c:865
do_group_exit+0x100/0x2e0 kernel/exit.c:962
get_signal+0x38d/0x1ca0 kernel/signal.c:2423
do_signal+0x7c/0x1550 arch/x86/kernel/signal.c:814
exit_to_usermode_loop+0x160/0x200 arch/x86/entry/common.c:160
prepare_exit_to_usermode arch/x86/entry/common.c:199 [inline]
syscall_return_slowpath arch/x86/entry/common.c:270 [inline]
do_syscall_64+0x4a3/0x640 arch/x86/entry/common.c:297
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45de59
RSP: 002b:00007f2b7bc44cf8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 000000000118bf28 RCX: 000000000045de59
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 000000000118bf28
RBP: 000000000118bf20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118bf2c
R13: 00007ffc802d0a7f R14: 00007f2b7bc459c0 R15: 000000000118bf2c

Showing all locks held in the system:
1 lock held by khungtaskd/1531:
#0: (tasklist_lock){.+.+}, at: [<ffffffff81430a04>] debug_show_all_locks+0x7c/0x21a kernel/locking/lockdep.c:4548
1 lock held by in:imklog/7755:
#0: (&f->f_pos_lock){+.+.}, at: [<ffffffff818f88cb>] __fdget_pos+0x1fb/0x2b0 fs/file.c:769
2 locks held by agetty/7925:
#0: (&tty->ldisc_sem){++++}, at: [<ffffffff835e20b2>] tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:284
#1: (&tty->atomic_write_lock){+.+.}, at: [<ffffffff835ca35d>] tty_write_lock drivers/tty/tty_io.c:885 [inline]
#1: (&tty->atomic_write_lock){+.+.}, at: [<ffffffff835ca35d>] do_tty_write drivers/tty/tty_io.c:908 [inline]
#1: (&tty->atomic_write_lock){+.+.}, at: [<ffffffff835ca35d>] tty_write+0x22d/0x740 drivers/tty/tty_io.c:1043
5 locks held by kworker/0:4/8074:
#0: ("usb_hub_wq"){+.+.}, at: [<ffffffff813733a0>] process_one_work+0x6b0/0x14a0 kernel/workqueue.c:2087
#1: ((&hub->events)){+.+.}, at: [<ffffffff813733d6>] process_one_work+0x6e6/0x14a0 kernel/workqueue.c:2091
#2: (&dev->mutex){....}, at: [<ffffffff84529398>] device_lock include/linux/device.h:1081 [inline]
#2: (&dev->mutex){....}, at: [<ffffffff84529398>] hub_event+0x108/0x3dc0 drivers/usb/core/hub.c:5220
#3: (&port_dev->status_lock){+.+.}, at: [<ffffffff8452ab9e>] usb_lock_port drivers/usb/core/hub.c:2934 [inline]
#3: (&port_dev->status_lock){+.+.}, at: [<ffffffff8452ab9e>] hub_port_connect drivers/usb/core/hub.c:4904 [inline]
#3: (&port_dev->status_lock){+.+.}, at: [<ffffffff8452ab9e>] hub_port_connect_change drivers/usb/core/hub.c:5088 [inline]
#3: (&port_dev->status_lock){+.+.}, at: [<ffffffff8452ab9e>] port_event drivers/usb/core/hub.c:5194 [inline]
#3: (&port_dev->status_lock){+.+.}, at: [<ffffffff8452ab9e>] hub_event+0x190e/0x3dc0 drivers/usb/core/hub.c:5274
#4: (hcd->address0_mutex){+.+.}, at: [<ffffffff8451eedb>] hub_port_init+0x15b/0x2970 drivers/usb/core/hub.c:4429
1 lock held by syz-executor.2/17202:
#0: (&dev->mutex){....}, at: [<ffffffff8455bfe3>] device_lock include/linux/device.h:1081 [inline]
#0: (&dev->mutex){....}, at: [<ffffffff8455bfe3>] usbdev_release+0x73/0x380 drivers/usb/core/devio.c:1066
1 lock held by syz-executor.1/23651:
#0: (&lo->lo_ctl_mutex/1){+.+.}, at: [<ffffffff839806a7>] lo_ioctl+0x87/0x1cd0 drivers/block/loop.c:1414
1 lock held by syz-executor.3/23669:
#0: (&type->s_umount_key#63/1){+.+.}, at: [<ffffffff81898ad6>] alloc_super fs/super.c:251 [inline]
#0: (&type->s_umount_key#63/1){+.+.}, at: [<ffffffff81898ad6>] sget_userns+0x556/0xc10 fs/super.c:516
1 lock held by syz-executor.2/23685:
#0: (&type->s_umount_key#63/1){+.+.}, at: [<ffffffff81898ad6>] alloc_super fs/super.c:251 [inline]
#0: (&type->s_umount_key#63/1){+.+.}, at: [<ffffffff81898ad6>] sget_userns+0x556/0xc10 fs/super.c:516

=============================================

NMI backtrace for cpu 0
CPU: 0 PID: 1531 Comm: khungtaskd Not tainted 4.14.202-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x283 lib/dump_stack.c:58
nmi_cpu_backtrace.cold+0x57/0x93 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x13a/0x17f lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:140 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:195 [inline]
watchdog+0x5b9/0xb40 kernel/hung_task.c:274
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 5 Comm: kworker/u4:0 Not tainted 4.14.202-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: bat_events batadv_nc_worker
task: ffff8880b5ff2140 task.stack: ffff8880b5ff8000
RIP: 0010:native_apic_mem_write+0x0/0x10 arch/x86/include/asm/apic.h:95
RSP: 0018:ffff8880ba507fc0 EFLAGS: 00000046
RAX: dffffc0000000000 RBX: ffffffff88cbd000 RCX: 0000000000000000
RDX: 1ffffffff1197a1e RSI: 0000000000000000 RDI: 00000000000000b0
RBP: 0000000000000000 R08: ffff88823fff7058 R09: ffff88823fff704f
R10: ffff88823fff7057 R11: 000000c9b90e9b60 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005560577c1160 CR3: 0000000058ac2000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
apic_eoi arch/x86/include/asm/apic.h:400 [inline]
ack_APIC_irq arch/x86/include/asm/apic.h:444 [inline]
entering_ack_irq arch/x86/include/asm/apic.h:636 [inline]
smp_apic_timer_interrupt+0x88/0x5e0 arch/x86/kernel/apic/apic.c:1098
apic_timer_interrupt+0x93/0xa0 arch/x86/entry/entry_64.S:793
</IRQ>
RIP: 0010:should_resched arch/x86/include/asm/preempt.h:99 [inline]
RIP: 0010:__local_bh_enable_ip+0xed/0x170 kernel/softirq.c:192
RSP: 0018:ffff8880b5fffc50 EFLAGS: 00000282 ORIG_RAX: ffffffffffffff10
RAX: 1ffffffff11e121b RBX: 0000000000000201 RCX: 1ffff11016bfe542
RDX: dffffc0000000000 RSI: ffff8880b5ff29f0 RDI: ffff8880b5ff29c4
RBP: ffffffff8707ea3c R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: dffffc0000000000
R13: ffffffff87080550 R14: ffff8880619e19a8 R15: ffff888061931b40
spin_unlock_bh include/linux/spinlock.h:362 [inline]
batadv_nc_purge_paths+0x20c/0x300 net/batman-adv/network-coding.c:479
batadv_nc_worker+0x628/0xc50 net/batman-adv/network-coding.c:727
process_one_work+0x793/0x14a0 kernel/workqueue.c:2116
worker_thread+0x5cc/0xff0 kernel/workqueue.c:2250
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
Code: 38 d0 7c 04 84 d2 75 13 83 3d 2c 90 09 0a 01 7f 02 5d c3 89 ef 5d e9 e5 c7 fe ff 48 c7 c7 c0 c3 2c 8b e8 44 da 5d 00 eb df 66 90 <89> ff 89 b7 00 c0 5f ff c3 0f 1f 80 00 00 00 00 48 b8 00 00 00

syzbot

unread,
Feb 21, 2021, 5:17:13 PM2/21/21
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.

syzbot

unread,
Apr 27, 2021, 2:36:16 AM4/27/21
to syzkaller...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages