[v6.1] INFO: task hung in migrate_pages (2)
0 views
Skip to first unread message
syzbot
Mar 20, 2024, 8:05:34 AMMar 20
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: d7543167affd Linux 6.1.82
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1386def1180000
kernel config: https://syzkaller.appspot.com/x/.config?x=59059e181681c079
dashboard link: https://syzkaller.appspot.com/bug?extid=632c698e69b78c2e88d2
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/88220954516a/disk-d7543167.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c9062e074717/vmlinux-d7543167.xz
kernel image: https://storage.googleapis.com/syzbot-assets/70391b45a752/bzImage-d7543167.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+632c69...@syzkaller.appspotmail.com
INFO: task kcompactd0:31 blocked for more than 143 seconds.
Not tainted 6.1.82-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kcompactd0 state:D stack:24352 pid:31 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
io_schedule+0x88/0x100 kernel/sched/core.c:8786
folio_wait_bit_common+0x878/0x1290 mm/filemap.c:1296
__unmap_and_move mm/migrate.c:1038 [inline]
unmap_and_move mm/migrate.c:1192 [inline]
migrate_pages+0xaa7/0x4070 mm/migrate.c:1469
compact_zone+0x2aef/0x41e0 mm/compaction.c:2414
proactive_compact_node mm/compaction.c:2666 [inline]
kcompactd+0x1862/0x28e0 mm/compaction.c:2976
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:307
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8d12ab10 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8d12b310 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
#0: ffffffff8d12a940 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:319 [inline]
#0: ffffffff8d12a940 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:760 [inline]
#0: ffffffff8d12a940 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6494
2 locks held by getty/3306:
#0: ffff888028ce1098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc900031262f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2188
3 locks held by kworker/0:6/3628:
#0: ffff888012470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90004b2fd20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffffffff8d12ff38 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:291 [inline]
#2: ffffffff8d12ff38 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3b0/0x8a0 kernel/rcu/tree_exp.h:949
5 locks held by kworker/1:4/3629:
#0: ffff8881446bfd38 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1:
ffffc90004b3fd20 ((work_completion)(&hub->events)){+.+.}-{0:0}
, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffff888146301190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#2: ffff888146301190 (&dev->mutex){....}-{3:3}, at: hub_event+0x1fe/0x5730 drivers/usb/core/hub.c:5780
#3: ffff88807d1f9190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#3: ffff88807d1f9190 (&dev->mutex){....}-{3:3}, at: __device_attach+0x8a/0x570 drivers/base/dd.c:990
#4: ffff8880223a8118 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#4: ffff8880223a8118 (&dev->mutex){....}-{3:3}, at: __device_attach+0x8a/0x570 drivers/base/dd.c:990
3 locks held by kworker/u4:6/3907:
2 locks held by kworker/0:10/6019:
#0: ffff888012472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90012f87d20 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
3 locks held by kworker/0:14/6025:
4 locks held by kworker/0:0/24636:
#0: ffff8880b983aa18 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:537
#1: ffff8880b9827788 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x43d/0x770 kernel/sched/psi.c:1000
#2: ffff8880b9827788 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_change+0xf9/0x270 kernel/sched/psi.c:924
#3: ffffffff8d12a8c0 (rcu_read_lock_sched){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:319 [inline]
#3: ffffffff8d12a8c0 (rcu_read_lock_sched){....}-{1:2}, at: rcu_read_lock_sched include/linux/rcupdate.h:852 [inline]
#3: ffffffff8d12a8c0 (rcu_read_lock_sched){....}-{1:2}, at: pfn_valid include/linux/mmzone.h:1857 [inline]
#3: ffffffff8d12a8c0 (rcu_read_lock_sched){....}-{1:2}, at: __virt_addr_valid+0x17f/0x520 arch/x86/mm/physaddr.c:65
1 lock held by syz-executor.0/24647:
1 lock held by syz-executor.3/24754:
7 locks held by kworker/0:1/24959:
#0: ffff8881446bfd38 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc9000452fd20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffff888145fe9190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#2: ffff888145fe9190 (&dev->mutex){....}-{3:3}, at: hub_event+0x1fe/0x5730 drivers/usb/core/hub.c:5780
#3: ffff888145fec4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3144 [inline]
#3: ffff888145fec4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5352 [inline]
#3: ffff888145fec4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5596 [inline]
#3: ffff888145fec4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5752 [inline]
#3: ffff888145fec4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x31e5/0x5730 drivers/usb/core/hub.c:5834
#4: ffff888021c23d68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5353 [inline]
#4: ffff888021c23d68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5596 [inline]
#4: ffff888021c23d68 (hcd->address0_mutex){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5752 [inline]
#4: ffff888021c23d68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_event+0x3213/0x5730 drivers/usb/core/hub.c:5834
#5: ffffffff8dc33270 (ehci_cf_port_reset_rwsem){.+.+}-{3:3}, at: hub_port_reset+0x1f4/0x1f00 drivers/usb/core/hub.c:3001
#6: ffff8880b983aa18 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:537
4 locks held by syz-executor.0/26326:
6 locks held by kworker/1:3/26372:
#0: ffff8881446bfd38 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90006b87d20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffff888145fb9190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#2: ffff888145fb9190 (&dev->mutex){....}-{3:3}, at: hub_event+0x1fe/0x5730 drivers/usb/core/hub.c:5780
#3: ffff888145fbc4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3144 [inline]
#3: ffff888145fbc4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5352 [inline]
#3: ffff888145fbc4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5596 [inline]
#3: ffff888145fbc4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5752 [inline]
#3: ffff888145fbc4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x31e5/0x5730 drivers/usb/core/hub.c:5834
#4: ffff888145be3d68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5353 [inline]
#4: ffff888145be3d68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5596 [inline]
#4: ffff888145be3d68 (hcd->address0_mutex){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5752 [inline]
#4: ffff888145be3d68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_event+0x3213/0x5730 drivers/usb/core/hub.c:5834
#5: ffffffff8dc33270 (ehci_cf_port_reset_rwsem){.+.+}-{3:3}, at: hub_port_reset+0x1f4/0x1f00 drivers/usb/core/hub.c:3001
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.1.82-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x4e1/0x560 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1b0/0x3f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
watchdog+0xf88/0xfd0 kernel/hung_task.c:377
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:307
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 24959 Comm: kworker/0:1 Not tainted 6.1.82-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Workqueue: usb_hub_wq hub_event
RIP: 0010:kasan_check_range+0x1ac/0x290 mm/kasan/generic.c:189
Code: 4c 89 d5 48 8d 5d 07 48 85 ed 48 0f 49 dd 48 83 e3 f8 48 29 dd 74 12 41 80 39 00 0f 85 a2 00 00 00 49 ff c1 48 ff cd 75 ee 5b <41> 5e 41 5f 5d c3 45 84 f6 75 61 41 f7 c6 00 ff 00 00 75 5d 41 f7
RSP: 0018:ffffc9000452eec0 EFLAGS: 00000056
RAX: 0000000000000001 RBX: 0000000000000000 RCX: ffffffff816a7857
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8e7362a8
RBP: 0000000000000001 R08: dffffc0000000000 R09: fffffbfff1ce6c56
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff920008a5de8
R13: ffffffff815ee449 R14: fffffbfff1ce6c56 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020001f40 CR3: 0000000069fae000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
instrument_atomic_read include/linux/instrumented.h:72 [inline]
_test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline]
cpumask_test_cpu include/linux/cpumask.h:444 [inline]
cpu_online include/linux/cpumask.h:1030 [inline]
trace_lock_release include/trace/events/lock.h:69 [inline]
lock_release+0xc7/0xa20 kernel/locking/lockdep.c:5673
__raw_spin_unlock include/linux/spinlock_api_smp.h:141 [inline]
_raw_spin_unlock+0x12/0x40 kernel/locking/spinlock.c:186
raw_spin_rq_unlock kernel/sched/core.c:581 [inline]
rq_unlock kernel/sched/sched.h:1669 [inline]
ttwu_queue kernel/sched/core.c:3906 [inline]
try_to_wake_up+0x7c9/0x12e0 kernel/sched/core.c:4228
wake_up_worker kernel/workqueue.c:859 [inline]
wq_worker_sleeping+0x1b9/0x270 kernel/workqueue.c:929
sched_submit_work kernel/sched/core.c:6598 [inline]
schedule+0x6b/0x180 kernel/sched/core.c:6631
schedule_timeout+0x1b9/0x300 kernel/time/timer.c:1935
do_wait_for_common kernel/sched/completion.c:85 [inline]
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion_timeout+0x324/0x630 kernel/sched/completion.c:157
usb_start_wait_urb+0x16b/0x510 drivers/usb/core/message.c:63
usb_internal_control_msg drivers/usb/core/message.c:102 [inline]
usb_control_msg+0x2ad/0x4c0 drivers/usb/core/message.c:153
set_port_feature drivers/usb/core/hub.c:457 [inline]
hub_port_reset+0x4d2/0x1f00 drivers/usb/core/hub.c:3017
hub_port_init+0x286/0x27e0 drivers/usb/core/hub.c:4826
hub_port_connect drivers/usb/core/hub.c:5385 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5596 [inline]
port_event drivers/usb/core/hub.c:5752 [inline]
hub_event+0x2b31/0x5730 drivers/usb/core/hub.c:5834
process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:307
</TASK>
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot found the following issue on:
HEAD commit: d7543167affd Linux 6.1.82
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1386def1180000
kernel config: https://syzkaller.appspot.com/x/.config?x=59059e181681c079
dashboard link: https://syzkaller.appspot.com/bug?extid=632c698e69b78c2e88d2
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/88220954516a/disk-d7543167.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c9062e074717/vmlinux-d7543167.xz
kernel image: https://storage.googleapis.com/syzbot-assets/70391b45a752/bzImage-d7543167.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+632c69...@syzkaller.appspotmail.com
INFO: task kcompactd0:31 blocked for more than 143 seconds.
Not tainted 6.1.82-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kcompactd0 state:D stack:24352 pid:31 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
io_schedule+0x88/0x100 kernel/sched/core.c:8786
folio_wait_bit_common+0x878/0x1290 mm/filemap.c:1296
__unmap_and_move mm/migrate.c:1038 [inline]
unmap_and_move mm/migrate.c:1192 [inline]
migrate_pages+0xaa7/0x4070 mm/migrate.c:1469
compact_zone+0x2aef/0x41e0 mm/compaction.c:2414
proactive_compact_node mm/compaction.c:2666 [inline]
kcompactd+0x1862/0x28e0 mm/compaction.c:2976
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:307
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8d12ab10 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8d12b310 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xe30 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
#0: ffffffff8d12a940 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:319 [inline]
#0: ffffffff8d12a940 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:760 [inline]
#0: ffffffff8d12a940 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6494
2 locks held by getty/3306:
#0: ffff888028ce1098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc900031262f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2188
3 locks held by kworker/0:6/3628:
#0: ffff888012470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90004b2fd20 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffffffff8d12ff38 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:291 [inline]
#2: ffffffff8d12ff38 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3b0/0x8a0 kernel/rcu/tree_exp.h:949
5 locks held by kworker/1:4/3629:
#0: ffff8881446bfd38 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1:
ffffc90004b3fd20 ((work_completion)(&hub->events)){+.+.}-{0:0}
, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffff888146301190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#2: ffff888146301190 (&dev->mutex){....}-{3:3}, at: hub_event+0x1fe/0x5730 drivers/usb/core/hub.c:5780
#3: ffff88807d1f9190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#3: ffff88807d1f9190 (&dev->mutex){....}-{3:3}, at: __device_attach+0x8a/0x570 drivers/base/dd.c:990
#4: ffff8880223a8118 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#4: ffff8880223a8118 (&dev->mutex){....}-{3:3}, at: __device_attach+0x8a/0x570 drivers/base/dd.c:990
3 locks held by kworker/u4:6/3907:
2 locks held by kworker/0:10/6019:
#0: ffff888012472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90012f87d20 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
3 locks held by kworker/0:14/6025:
4 locks held by kworker/0:0/24636:
#0: ffff8880b983aa18 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:537
#1: ffff8880b9827788 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x43d/0x770 kernel/sched/psi.c:1000
#2: ffff8880b9827788 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_change+0xf9/0x270 kernel/sched/psi.c:924
#3: ffffffff8d12a8c0 (rcu_read_lock_sched){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:319 [inline]
#3: ffffffff8d12a8c0 (rcu_read_lock_sched){....}-{1:2}, at: rcu_read_lock_sched include/linux/rcupdate.h:852 [inline]
#3: ffffffff8d12a8c0 (rcu_read_lock_sched){....}-{1:2}, at: pfn_valid include/linux/mmzone.h:1857 [inline]
#3: ffffffff8d12a8c0 (rcu_read_lock_sched){....}-{1:2}, at: __virt_addr_valid+0x17f/0x520 arch/x86/mm/physaddr.c:65
1 lock held by syz-executor.0/24647:
1 lock held by syz-executor.3/24754:
7 locks held by kworker/0:1/24959:
#0: ffff8881446bfd38 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc9000452fd20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffff888145fe9190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#2: ffff888145fe9190 (&dev->mutex){....}-{3:3}, at: hub_event+0x1fe/0x5730 drivers/usb/core/hub.c:5780
#3: ffff888145fec4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3144 [inline]
#3: ffff888145fec4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5352 [inline]
#3: ffff888145fec4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5596 [inline]
#3: ffff888145fec4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5752 [inline]
#3: ffff888145fec4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x31e5/0x5730 drivers/usb/core/hub.c:5834
#4: ffff888021c23d68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5353 [inline]
#4: ffff888021c23d68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5596 [inline]
#4: ffff888021c23d68 (hcd->address0_mutex){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5752 [inline]
#4: ffff888021c23d68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_event+0x3213/0x5730 drivers/usb/core/hub.c:5834
#5: ffffffff8dc33270 (ehci_cf_port_reset_rwsem){.+.+}-{3:3}, at: hub_port_reset+0x1f4/0x1f00 drivers/usb/core/hub.c:3001
#6: ffff8880b983aa18 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:537
4 locks held by syz-executor.0/26326:
6 locks held by kworker/1:3/26372:
#0: ffff8881446bfd38 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#1: ffffc90006b87d20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7a9/0x11d0 kernel/workqueue.c:2267
#2: ffff888145fb9190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:837 [inline]
#2: ffff888145fb9190 (&dev->mutex){....}-{3:3}, at: hub_event+0x1fe/0x5730 drivers/usb/core/hub.c:5780
#3: ffff888145fbc4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3144 [inline]
#3: ffff888145fbc4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5352 [inline]
#3: ffff888145fbc4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5596 [inline]
#3: ffff888145fbc4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5752 [inline]
#3: ffff888145fbc4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x31e5/0x5730 drivers/usb/core/hub.c:5834
#4: ffff888145be3d68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5353 [inline]
#4: ffff888145be3d68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5596 [inline]
#4: ffff888145be3d68 (hcd->address0_mutex){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5752 [inline]
#4: ffff888145be3d68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_event+0x3213/0x5730 drivers/usb/core/hub.c:5834
#5: ffffffff8dc33270 (ehci_cf_port_reset_rwsem){.+.+}-{3:3}, at: hub_port_reset+0x1f4/0x1f00 drivers/usb/core/hub.c:3001
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.1.82-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x4e1/0x560 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1b0/0x3f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
watchdog+0xf88/0xfd0 kernel/hung_task.c:377
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:307
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 24959 Comm: kworker/0:1 Not tainted 6.1.82-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Workqueue: usb_hub_wq hub_event
RIP: 0010:kasan_check_range+0x1ac/0x290 mm/kasan/generic.c:189
Code: 4c 89 d5 48 8d 5d 07 48 85 ed 48 0f 49 dd 48 83 e3 f8 48 29 dd 74 12 41 80 39 00 0f 85 a2 00 00 00 49 ff c1 48 ff cd 75 ee 5b <41> 5e 41 5f 5d c3 45 84 f6 75 61 41 f7 c6 00 ff 00 00 75 5d 41 f7
RSP: 0018:ffffc9000452eec0 EFLAGS: 00000056
RAX: 0000000000000001 RBX: 0000000000000000 RCX: ffffffff816a7857
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8e7362a8
RBP: 0000000000000001 R08: dffffc0000000000 R09: fffffbfff1ce6c56
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff920008a5de8
R13: ffffffff815ee449 R14: fffffbfff1ce6c56 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020001f40 CR3: 0000000069fae000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
instrument_atomic_read include/linux/instrumented.h:72 [inline]
_test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline]
cpumask_test_cpu include/linux/cpumask.h:444 [inline]
cpu_online include/linux/cpumask.h:1030 [inline]
trace_lock_release include/trace/events/lock.h:69 [inline]
lock_release+0xc7/0xa20 kernel/locking/lockdep.c:5673
__raw_spin_unlock include/linux/spinlock_api_smp.h:141 [inline]
_raw_spin_unlock+0x12/0x40 kernel/locking/spinlock.c:186
raw_spin_rq_unlock kernel/sched/core.c:581 [inline]
rq_unlock kernel/sched/sched.h:1669 [inline]
ttwu_queue kernel/sched/core.c:3906 [inline]
try_to_wake_up+0x7c9/0x12e0 kernel/sched/core.c:4228
wake_up_worker kernel/workqueue.c:859 [inline]
wq_worker_sleeping+0x1b9/0x270 kernel/workqueue.c:929
sched_submit_work kernel/sched/core.c:6598 [inline]
schedule+0x6b/0x180 kernel/sched/core.c:6631
schedule_timeout+0x1b9/0x300 kernel/time/timer.c:1935
do_wait_for_common kernel/sched/completion.c:85 [inline]
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion_timeout+0x324/0x630 kernel/sched/completion.c:157
usb_start_wait_urb+0x16b/0x510 drivers/usb/core/message.c:63
usb_internal_control_msg drivers/usb/core/message.c:102 [inline]
usb_control_msg+0x2ad/0x4c0 drivers/usb/core/message.c:153
set_port_feature drivers/usb/core/hub.c:457 [inline]
hub_port_reset+0x4d2/0x1f00 drivers/usb/core/hub.c:3017
hub_port_init+0x286/0x27e0 drivers/usb/core/hub.c:4826
hub_port_connect drivers/usb/core/hub.c:5385 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5596 [inline]
port_event drivers/usb/core/hub.c:5752 [inline]
hub_event+0x2b31/0x5730 drivers/usb/core/hub.c:5834
process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:307
</TASK>
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages