[v5.15] INFO: task hung in rfkill_global_led_trigger_worker
0 views
Skip to first unread message
syzbot
Mar 8, 2023, 11:06:43 AM3/8/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: d9b4a0c83a2d Linux 5.15.98
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1498ef04c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=2f8d9515b973b23b
dashboard link: https://syzkaller.appspot.com/bug?extid=24f226fac8e2ac7ed1cd
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/037cabbd3313/disk-d9b4a0c8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9967e551eb34/vmlinux-d9b4a0c8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a050c7a4fd99/bzImage-d9b4a0c8.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+24f226...@syzkaller.appspotmail.com
INFO: task kworker/1:32:8470 blocked for more than 143 seconds.
Not tainted 5.15.98-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:32 state:D stack:24192 pid: 8470 ppid: 2 flags:0x00004000
Workqueue: events rfkill_global_led_trigger_worker
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0x132d/0x45e0 kernel/sched/core.c:6369
schedule+0x11b/0x1f0 kernel/sched/core.c:6452
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6511
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
rfkill_global_led_trigger_worker+0x23/0xd0 net/rfkill/core.c:181
process_one_work+0x8e6/0x1230 kernel/workqueue.c:2306
worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 <unknown>:298
</TASK>
INFO: task syz-executor.3:21233 blocked for more than 143 seconds.
Not tainted 5.15.98-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.3 state:D stack:26360 pid:21233 ppid: 3622 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0x132d/0x45e0 kernel/sched/core.c:6369
schedule+0x11b/0x1f0 kernel/sched/core.c:6452
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6511
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
rfkill_unregister+0xcc/0x220 net/rfkill/core.c:1118
nfc_unregister_device+0x92/0x290 net/nfc/core.c:1167
virtual_ncidev_close+0x55/0x90 drivers/nfc/virtual_ncidev.c:166
__fput+0x3bf/0x890 fs/file_table.c:280
task_work_run+0x129/0x1a0 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:175
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:207
__syscall_exit_to_user_mode_work kernel/entry/common.c:289 [inline]
syscall_exit_to_user_mode+0x5d/0x2a0 kernel/entry/common.c:300
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fb1e29ebfab
RSP: 002b:00007ffc59363ac0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000006 RCX: 00007fb1e29ebfab
RDX: 0000000000000000 RSI: 0000001b2cf209c8 RDI: 0000000000000005
RBP: 00007fb1e2b5b980 R08: 0000000000000000 R09: 0000000005801ce4
R10: 0000000000000000 R11: 0000000000000293 R12: 000000000012fd74
R13: 00007ffc59363bc0 R14: 00007ffc59363be0 R15: 0000000000000032
</TASK>
Showing all locks held in the system:
3 locks held by kworker/u4:0/9:
1 lock held by khungtaskd/27:
#0: ffffffff8c91c660 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3271:
#0: ffff888023f27098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002bb32e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1da0 drivers/tty/n_tty.c:2147
3 locks held by kworker/1:32/8470:
#0: ffff888011c64d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x1230 kernel/workqueue.c:2279
#1: ffffc9000407fd20 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_one_work+0x7cd/0x1230 kernel/workqueue.c:2281
#2: ffffffff8dc65b68 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_global_led_trigger_worker+0x23/0xd0 net/rfkill/core.c:181
2 locks held by syz-executor.1/21237:
#0: ffffffff8dc65b68 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_write+0x1a5/0x790 net/rfkill/core.c:1266
#1: ffff888057a3e190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#1: ffff888057a3e190 (&dev->mutex){....}-{3:3}, at: nfc_dev_down net/nfc/core.c:143 [inline]
#1: ffff888057a3e190 (&dev->mutex){....}-{3:3}, at: nfc_rfkill_set_block+0x4c/0x2f0 net/nfc/core.c:179
2 locks held by syz-executor.3/21233:
#0: ffff888057a3e190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#0: ffff888057a3e190 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x5f/0x290 net/nfc/core.c:1165
#1: ffffffff8dc65b68 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xcc/0x220 net/rfkill/core.c:1118
2 locks held by syz-executor.3/21438:
#0: ffff88805a00f118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x34/0x590 drivers/bluetooth/hci_vhci.c:149
#1: ffffffff8dc65b68 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x30/0x880 net/rfkill/core.c:1045
2 locks held by syz-executor.1/21439:
#0: ffff88805a00cd18 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x34/0x590 drivers/bluetooth/hci_vhci.c:149
#1: ffffffff8dc65b68 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x30/0x880 net/rfkill/core.c:1045
2 locks held by syz-executor.3/21442:
#0: ffff888059c0c918 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x34/0x590 drivers/bluetooth/hci_vhci.c:149
#1: ffffffff8dc65b68 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x30/0x880 net/rfkill/core.c:1045
2 locks held by syz-executor.1/21444:
#0: ffff88805a4e8d18 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x34/0x590 drivers/bluetooth/hci_vhci.c:149
#1: ffffffff8dc65b68 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x30/0x880 net/rfkill/core.c:1045
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.98-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xec6/0xf10 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 <unknown>:298
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 17037 Comm: kworker/1:5 Not tainted 5.15.98-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: events nsim_dev_trap_report_work
RIP: 0010:__lock_release kernel/locking/lockdep.c:5278 [inline]
RIP: 0010:lock_release+0x1a0/0x9c0 kernel/locking/lockdep.c:5642
Code: 80 3c 3b 00 74 08 4c 89 f7 e8 5c b5 66 00 4c 8b ac 24 b0 00 00 00 fa 48 c7 c7 60 0d 8b 8a e8 87 1b b8 08 65 ff 05 40 a6 9f 7e <48> 8d 9c 24 80 00 00 00 48 c1 eb 03 42 0f b6 04 3b 84 c0 0f 85 92
RSP: 0018:ffffc900057bf780 EFLAGS: 00000002
RAX: 0000000000000001 RBX: 1ffff92000af7f06 RCX: 0000000080000002
RDX: 0000000000000000 RSI: ffffffff8a8b0d60 RDI: ffffffff8ad8b900
RBP: ffffc900057bf8b0 R08: dffffc0000000000 R09: fffffbfff1bc70fe
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff92000af7efc
R13: 0000000000000046 R14: ffffc900057bf830 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005597db3bc680 CR3: 0000000023023000 CR4: 00000000003506e0
Call Trace:
<TASK>
crng_make_state+0x39e/0x690 drivers/char/random.c:392
_get_random_bytes+0xd3/0x2b0 drivers/char/random.c:405
nsim_dev_trap_skb_build drivers/net/netdevsim/dev.c:694 [inline]
nsim_dev_trap_report drivers/net/netdevsim/dev.c:724 [inline]
nsim_dev_trap_report_work+0x64e/0xab0 drivers/net/netdevsim/dev.c:765
process_one_work+0x8e6/0x1230 kernel/workqueue.c:2306
worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 <unknown>:298
</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.
syzbot found the following issue on:
HEAD commit: d9b4a0c83a2d Linux 5.15.98
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1498ef04c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=2f8d9515b973b23b
dashboard link: https://syzkaller.appspot.com/bug?extid=24f226fac8e2ac7ed1cd
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/037cabbd3313/disk-d9b4a0c8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9967e551eb34/vmlinux-d9b4a0c8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a050c7a4fd99/bzImage-d9b4a0c8.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+24f226...@syzkaller.appspotmail.com
INFO: task kworker/1:32:8470 blocked for more than 143 seconds.
Not tainted 5.15.98-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:32 state:D stack:24192 pid: 8470 ppid: 2 flags:0x00004000
Workqueue: events rfkill_global_led_trigger_worker
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0x132d/0x45e0 kernel/sched/core.c:6369
schedule+0x11b/0x1f0 kernel/sched/core.c:6452
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6511
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
rfkill_global_led_trigger_worker+0x23/0xd0 net/rfkill/core.c:181
process_one_work+0x8e6/0x1230 kernel/workqueue.c:2306
worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 <unknown>:298
</TASK>
INFO: task syz-executor.3:21233 blocked for more than 143 seconds.
Not tainted 5.15.98-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.3 state:D stack:26360 pid:21233 ppid: 3622 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0x132d/0x45e0 kernel/sched/core.c:6369
schedule+0x11b/0x1f0 kernel/sched/core.c:6452
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6511
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
rfkill_unregister+0xcc/0x220 net/rfkill/core.c:1118
nfc_unregister_device+0x92/0x290 net/nfc/core.c:1167
virtual_ncidev_close+0x55/0x90 drivers/nfc/virtual_ncidev.c:166
__fput+0x3bf/0x890 fs/file_table.c:280
task_work_run+0x129/0x1a0 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:175
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:207
__syscall_exit_to_user_mode_work kernel/entry/common.c:289 [inline]
syscall_exit_to_user_mode+0x5d/0x2a0 kernel/entry/common.c:300
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fb1e29ebfab
RSP: 002b:00007ffc59363ac0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000006 RCX: 00007fb1e29ebfab
RDX: 0000000000000000 RSI: 0000001b2cf209c8 RDI: 0000000000000005
RBP: 00007fb1e2b5b980 R08: 0000000000000000 R09: 0000000005801ce4
R10: 0000000000000000 R11: 0000000000000293 R12: 000000000012fd74
R13: 00007ffc59363bc0 R14: 00007ffc59363be0 R15: 0000000000000032
</TASK>
Showing all locks held in the system:
3 locks held by kworker/u4:0/9:
1 lock held by khungtaskd/27:
#0: ffffffff8c91c660 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3271:
#0: ffff888023f27098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002bb32e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1da0 drivers/tty/n_tty.c:2147
3 locks held by kworker/1:32/8470:
#0: ffff888011c64d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x1230 kernel/workqueue.c:2279
#1: ffffc9000407fd20 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_one_work+0x7cd/0x1230 kernel/workqueue.c:2281
#2: ffffffff8dc65b68 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_global_led_trigger_worker+0x23/0xd0 net/rfkill/core.c:181
2 locks held by syz-executor.1/21237:
#0: ffffffff8dc65b68 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_write+0x1a5/0x790 net/rfkill/core.c:1266
#1: ffff888057a3e190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#1: ffff888057a3e190 (&dev->mutex){....}-{3:3}, at: nfc_dev_down net/nfc/core.c:143 [inline]
#1: ffff888057a3e190 (&dev->mutex){....}-{3:3}, at: nfc_rfkill_set_block+0x4c/0x2f0 net/nfc/core.c:179
2 locks held by syz-executor.3/21233:
#0: ffff888057a3e190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#0: ffff888057a3e190 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x5f/0x290 net/nfc/core.c:1165
#1: ffffffff8dc65b68 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xcc/0x220 net/rfkill/core.c:1118
2 locks held by syz-executor.3/21438:
#0: ffff88805a00f118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x34/0x590 drivers/bluetooth/hci_vhci.c:149
#1: ffffffff8dc65b68 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x30/0x880 net/rfkill/core.c:1045
2 locks held by syz-executor.1/21439:
#0: ffff88805a00cd18 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x34/0x590 drivers/bluetooth/hci_vhci.c:149
#1: ffffffff8dc65b68 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x30/0x880 net/rfkill/core.c:1045
2 locks held by syz-executor.3/21442:
#0: ffff888059c0c918 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x34/0x590 drivers/bluetooth/hci_vhci.c:149
#1: ffffffff8dc65b68 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x30/0x880 net/rfkill/core.c:1045
2 locks held by syz-executor.1/21444:
#0: ffff88805a4e8d18 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x34/0x590 drivers/bluetooth/hci_vhci.c:149
#1: ffffffff8dc65b68 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x30/0x880 net/rfkill/core.c:1045
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.98-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xec6/0xf10 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 <unknown>:298
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 17037 Comm: kworker/1:5 Not tainted 5.15.98-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: events nsim_dev_trap_report_work
RIP: 0010:__lock_release kernel/locking/lockdep.c:5278 [inline]
RIP: 0010:lock_release+0x1a0/0x9c0 kernel/locking/lockdep.c:5642
Code: 80 3c 3b 00 74 08 4c 89 f7 e8 5c b5 66 00 4c 8b ac 24 b0 00 00 00 fa 48 c7 c7 60 0d 8b 8a e8 87 1b b8 08 65 ff 05 40 a6 9f 7e <48> 8d 9c 24 80 00 00 00 48 c1 eb 03 42 0f b6 04 3b 84 c0 0f 85 92
RSP: 0018:ffffc900057bf780 EFLAGS: 00000002
RAX: 0000000000000001 RBX: 1ffff92000af7f06 RCX: 0000000080000002
RDX: 0000000000000000 RSI: ffffffff8a8b0d60 RDI: ffffffff8ad8b900
RBP: ffffc900057bf8b0 R08: dffffc0000000000 R09: fffffbfff1bc70fe
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff92000af7efc
R13: 0000000000000046 R14: ffffc900057bf830 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005597db3bc680 CR3: 0000000023023000 CR4: 00000000003506e0
Call Trace:
<TASK>
crng_make_state+0x39e/0x690 drivers/char/random.c:392
_get_random_bytes+0xd3/0x2b0 drivers/char/random.c:405
nsim_dev_trap_skb_build drivers/net/netdevsim/dev.c:694 [inline]
nsim_dev_trap_report drivers/net/netdevsim/dev.c:724 [inline]
nsim_dev_trap_report_work+0x64e/0xab0 drivers/net/netdevsim/dev.c:765
process_one_work+0x8e6/0x1230 kernel/workqueue.c:2306
worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 <unknown>:298
</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.
syzbot
Jun 3, 2023, 6:02:52 AM6/3/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 0ab06468cbd1 Linux 5.15.114
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=147db42d280000
kernel config: https://syzkaller.appspot.com/x/.config?x=9a2696a271d0eba
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=154fb659280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1723a5d1280000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8ff3613d3f6b/disk-0ab06468.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/eebe2d8c6813/vmlinux-0ab06468.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f30284c26197/Image-0ab06468.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+24f226...@syzkaller.appspotmail.com
INFO: task kworker/0:3:4021 blocked for more than 143 seconds.
Not tainted 5.15.114-syzkaller #0
Workqueue: events rfkill_global_led_trigger_worker
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
__mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
rfkill_global_led_trigger_worker+0x30/0xe4 net/rfkill/core.c:181
process_one_work+0x790/0x11b8 kernel/workqueue.c:2307
worker_thread+0x910/0x1034 kernel/workqueue.c:2454
kthread+0x37c/0x45c kernel/kthread.c:319
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
INFO: task syz-executor408:4037 blocked for more than 143 seconds.
Not tainted 5.15.114-syzkaller #0
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
__mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
rfkill_unregister+0xb8/0x210 net/rfkill/core.c:1118
nfc_unregister_device+0x98/0x290 net/nfc/core.c:1167
nci_unregister_device+0x1e0/0x22c net/nfc/nci/core.c:1306
virtual_ncidev_close+0x70/0xb0 drivers/nfc/virtual_ncidev.c:166
__fput+0x30c/0x7f0 fs/file_table.c:280
____fput+0x20/0x30 fs/file_table.c:308
task_work_run+0x130/0x1e4 kernel/task_work.c:164
exit_task_work include/linux/task_work.h:32 [inline]
do_exit+0x688/0x2134 kernel/exit.c:872
do_group_exit+0x110/0x268 kernel/exit.c:994
__do_sys_exit_group kernel/exit.c:1005 [inline]
__se_sys_exit_group kernel/exit.c:1003 [inline]
__wake_up_parent+0x0/0x60 kernel/exit.c:1003
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor408:4049 blocked for more than 143 seconds.
Not tainted 5.15.114-syzkaller #0
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
__mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
rfkill_fop_open+0x12c/0x5c8 net/rfkill/core.c:1151
misc_open+0x2f0/0x368 drivers/char/misc.c:141
chrdev_open+0x3e8/0x4fc fs/char_dev.c:414
do_dentry_open+0x780/0xed8 fs/open.c:826
vfs_open+0x7c/0x90 fs/open.c:956
do_open fs/namei.c:3538 [inline]
path_openat+0x1f28/0x26f0 fs/namei.c:3672
do_filp_open+0x1a8/0x3b4 fs/namei.c:3699
do_sys_openat2+0x128/0x3d8 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1238
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor408:4050 blocked for more than 143 seconds.
Not tainted 5.15.114-syzkaller #0
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
__mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
device_lock include/linux/device.h:760 [inline]
nfc_dev_down net/nfc/core.c:143 [inline]
nfc_rfkill_set_block+0x50/0x2d0 net/nfc/core.c:179
rfkill_set_block+0x18c/0x37c net/rfkill/core.c:345
rfkill_fop_write+0x594/0x750 net/rfkill/core.c:1274
vfs_write+0x280/0xb3c fs/read_write.c:592
ksys_write+0x15c/0x26c fs/read_write.c:647
__do_sys_write fs/read_write.c:659 [inline]
__se_sys_write fs/read_write.c:656 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:656
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor408:4051 blocked for more than 143 seconds.
Not tainted 5.15.114-syzkaller #0
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
__mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
misc_open+0x6c/0x368 drivers/char/misc.c:107
chrdev_open+0x3e8/0x4fc fs/char_dev.c:414
do_dentry_open+0x780/0xed8 fs/open.c:826
vfs_open+0x7c/0x90 fs/open.c:956
do_open fs/namei.c:3538 [inline]
path_openat+0x1f28/0x26f0 fs/namei.c:3672
do_filp_open+0x1a8/0x3b4 fs/namei.c:3699
do_sys_openat2+0x128/0x3d8 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1238
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor408:4052 blocked for more than 143 seconds.
Not tainted 5.15.114-syzkaller #0
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
__mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
misc_open+0x6c/0x368 drivers/char/misc.c:107
chrdev_open+0x3e8/0x4fc fs/char_dev.c:414
do_dentry_open+0x780/0xed8 fs/open.c:826
vfs_open+0x7c/0x90 fs/open.c:956
do_open fs/namei.c:3538 [inline]
path_openat+0x1f28/0x26f0 fs/namei.c:3672
do_filp_open+0x1a8/0x3b4 fs/namei.c:3699
do_sys_openat2+0x128/0x3d8 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1238
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor408:4053 blocked for more than 143 seconds.
Not tainted 5.15.114-syzkaller #0
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
__mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
misc_open+0x6c/0x368 drivers/char/misc.c:107
chrdev_open+0x3e8/0x4fc fs/char_dev.c:414
do_dentry_open+0x780/0xed8 fs/open.c:826
vfs_open+0x7c/0x90 fs/open.c:956
do_open fs/namei.c:3538 [inline]
path_openat+0x1f28/0x26f0 fs/namei.c:3672
do_filp_open+0x1a8/0x3b4 fs/namei.c:3699
do_sys_openat2+0x128/0x3d8 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1238
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Showing all locks held in the system:
2 locks held by getty/3724:
#0: ffff0000d2c0a098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff800018e102e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1200 drivers/tty/n_tty.c:2147
3 locks held by kworker/0:3/4021:
#0: ffff0000c0020d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2280
#1: ffff80001cbd7c00 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2282
#2: ffff800016c39528 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_global_led_trigger_worker+0x30/0xe4 net/rfkill/core.c:181
2 locks held by syz-executor408/4037:
#0: ffff0000d2e02190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#0: ffff0000d2e02190 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x6c/0x290 net/nfc/core.c:1165
#1: ffff800016c39528 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xb8/0x210 net/rfkill/core.c:1118
2 locks held by syz-executor408/4049:
#0: ffff800015a41848 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x6c/0x368 drivers/char/misc.c:107
#1: ffff800016c39528 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_open+0x12c/0x5c8 net/rfkill/core.c:1151
2 locks held by syz-executor408/4050:
#0: ffff800016c39528 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_write+0x250/0x750 net/rfkill/core.c:1266
#1: ffff0000d2e02190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#1: ffff0000d2e02190 (&dev->mutex){....}-{3:3}, at: nfc_dev_down net/nfc/core.c:143 [inline]
#1: ffff0000d2e02190 (&dev->mutex){....}-{3:3}, at: nfc_rfkill_set_block+0x50/0x2d0 net/nfc/core.c:179
1 lock held by syz-executor408/4051:
#0: ffff800015a41848 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x6c/0x368 drivers/char/misc.c:107
1 lock held by syz-executor408/4052:
#0: ffff800015a41848 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x6c/0x368 drivers/char/misc.c:107
1 lock held by syz-executor408/4053:
#0: ffff800015a41848 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x6c/0x368 drivers/char/misc.c:107
=============================================
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
HEAD commit: 0ab06468cbd1 Linux 5.15.114
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=147db42d280000
kernel config: https://syzkaller.appspot.com/x/.config?x=9a2696a271d0eba
dashboard link: https://syzkaller.appspot.com/bug?extid=24f226fac8e2ac7ed1cd
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=154fb659280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1723a5d1280000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8ff3613d3f6b/disk-0ab06468.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/eebe2d8c6813/vmlinux-0ab06468.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f30284c26197/Image-0ab06468.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+24f226...@syzkaller.appspotmail.com
Not tainted 5.15.114-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:3 state:D stack: 0 pid: 4021 ppid: 2 flags:0x00000008
Workqueue: events rfkill_global_led_trigger_worker
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
__mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
rfkill_global_led_trigger_worker+0x30/0xe4 net/rfkill/core.c:181
process_one_work+0x790/0x11b8 kernel/workqueue.c:2307
worker_thread+0x910/0x1034 kernel/workqueue.c:2454
kthread+0x37c/0x45c kernel/kthread.c:319
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
INFO: task syz-executor408:4037 blocked for more than 143 seconds.
Not tainted 5.15.114-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor408 state:D stack: 0 pid: 4037 ppid: 3998 flags:0x0000000c
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
__mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
rfkill_unregister+0xb8/0x210 net/rfkill/core.c:1118
nfc_unregister_device+0x98/0x290 net/nfc/core.c:1167
nci_unregister_device+0x1e0/0x22c net/nfc/nci/core.c:1306
virtual_ncidev_close+0x70/0xb0 drivers/nfc/virtual_ncidev.c:166
__fput+0x30c/0x7f0 fs/file_table.c:280
____fput+0x20/0x30 fs/file_table.c:308
task_work_run+0x130/0x1e4 kernel/task_work.c:164
exit_task_work include/linux/task_work.h:32 [inline]
do_exit+0x688/0x2134 kernel/exit.c:872
do_group_exit+0x110/0x268 kernel/exit.c:994
__do_sys_exit_group kernel/exit.c:1005 [inline]
__se_sys_exit_group kernel/exit.c:1003 [inline]
__wake_up_parent+0x0/0x60 kernel/exit.c:1003
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor408:4049 blocked for more than 143 seconds.
Not tainted 5.15.114-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor408 state:D stack: 0 pid: 4049 ppid: 3995 flags:0x00000001
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
__mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
rfkill_fop_open+0x12c/0x5c8 net/rfkill/core.c:1151
misc_open+0x2f0/0x368 drivers/char/misc.c:141
chrdev_open+0x3e8/0x4fc fs/char_dev.c:414
do_dentry_open+0x780/0xed8 fs/open.c:826
vfs_open+0x7c/0x90 fs/open.c:956
do_open fs/namei.c:3538 [inline]
path_openat+0x1f28/0x26f0 fs/namei.c:3672
do_filp_open+0x1a8/0x3b4 fs/namei.c:3699
do_sys_openat2+0x128/0x3d8 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1238
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor408:4050 blocked for more than 143 seconds.
Not tainted 5.15.114-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor408 state:D stack: 0 pid: 4050 ppid: 3996 flags:0x00000001
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
__mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
device_lock include/linux/device.h:760 [inline]
nfc_dev_down net/nfc/core.c:143 [inline]
nfc_rfkill_set_block+0x50/0x2d0 net/nfc/core.c:179
rfkill_set_block+0x18c/0x37c net/rfkill/core.c:345
rfkill_fop_write+0x594/0x750 net/rfkill/core.c:1274
vfs_write+0x280/0xb3c fs/read_write.c:592
ksys_write+0x15c/0x26c fs/read_write.c:647
__do_sys_write fs/read_write.c:659 [inline]
__se_sys_write fs/read_write.c:656 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:656
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor408:4051 blocked for more than 143 seconds.
Not tainted 5.15.114-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor408 state:D stack: 0 pid: 4051 ppid: 3997 flags:0x00000001
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
__mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
misc_open+0x6c/0x368 drivers/char/misc.c:107
chrdev_open+0x3e8/0x4fc fs/char_dev.c:414
do_dentry_open+0x780/0xed8 fs/open.c:826
vfs_open+0x7c/0x90 fs/open.c:956
do_open fs/namei.c:3538 [inline]
path_openat+0x1f28/0x26f0 fs/namei.c:3672
do_filp_open+0x1a8/0x3b4 fs/namei.c:3699
do_sys_openat2+0x128/0x3d8 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1238
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor408:4052 blocked for more than 143 seconds.
Not tainted 5.15.114-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor408 state:D stack: 0 pid: 4052 ppid: 3993 flags:0x00000001
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
__mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
misc_open+0x6c/0x368 drivers/char/misc.c:107
chrdev_open+0x3e8/0x4fc fs/char_dev.c:414
do_dentry_open+0x780/0xed8 fs/open.c:826
vfs_open+0x7c/0x90 fs/open.c:956
do_open fs/namei.c:3538 [inline]
path_openat+0x1f28/0x26f0 fs/namei.c:3672
do_filp_open+0x1a8/0x3b4 fs/namei.c:3699
do_sys_openat2+0x128/0x3d8 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1238
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor408:4053 blocked for more than 143 seconds.
Not tainted 5.15.114-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor408 state:D stack: 0 pid: 4053 ppid: 3992 flags:0x00000001
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0xf10/0x1e38 kernel/sched/core.c:6372
schedule+0x11c/0x1c8 kernel/sched/core.c:6455
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6514
__mutex_lock_common+0xba0/0x2154 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
misc_open+0x6c/0x368 drivers/char/misc.c:107
chrdev_open+0x3e8/0x4fc fs/char_dev.c:414
do_dentry_open+0x780/0xed8 fs/open.c:826
vfs_open+0x7c/0x90 fs/open.c:956
do_open fs/namei.c:3538 [inline]
path_openat+0x1f28/0x26f0 fs/namei.c:3672
do_filp_open+0x1a8/0x3b4 fs/namei.c:3699
do_sys_openat2+0x128/0x3d8 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_openat fs/open.c:1243 [inline]
__se_sys_openat fs/open.c:1238 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1238
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffff800014aa19a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:268
2 locks held by getty/3724:
#0: ffff0000d2c0a098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff800018e102e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1200 drivers/tty/n_tty.c:2147
3 locks held by kworker/0:3/4021:
#0: ffff0000c0020d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2280
#1: ffff80001cbd7c00 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2282
#2: ffff800016c39528 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_global_led_trigger_worker+0x30/0xe4 net/rfkill/core.c:181
2 locks held by syz-executor408/4037:
#0: ffff0000d2e02190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#0: ffff0000d2e02190 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x6c/0x290 net/nfc/core.c:1165
#1: ffff800016c39528 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xb8/0x210 net/rfkill/core.c:1118
2 locks held by syz-executor408/4049:
#0: ffff800015a41848 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x6c/0x368 drivers/char/misc.c:107
#1: ffff800016c39528 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_open+0x12c/0x5c8 net/rfkill/core.c:1151
2 locks held by syz-executor408/4050:
#0: ffff800016c39528 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_write+0x250/0x750 net/rfkill/core.c:1266
#1: ffff0000d2e02190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#1: ffff0000d2e02190 (&dev->mutex){....}-{3:3}, at: nfc_dev_down net/nfc/core.c:143 [inline]
#1: ffff0000d2e02190 (&dev->mutex){....}-{3:3}, at: nfc_rfkill_set_block+0x50/0x2d0 net/nfc/core.c:179
1 lock held by syz-executor408/4051:
#0: ffff800015a41848 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x6c/0x368 drivers/char/misc.c:107
1 lock held by syz-executor408/4052:
#0: ffff800015a41848 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x6c/0x368 drivers/char/misc.c:107
1 lock held by syz-executor408/4053:
#0: ffff800015a41848 (misc_mtx){+.+.}-{3:3}, at: misc_open+0x6c/0x368 drivers/char/misc.c:107
=============================================
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
Reply all
Reply to author
Forward
0 new messages