[v5.15] INFO: task hung in nfc_rfkill_set_block

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8020ae3c051d Linux 5.15.103
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1155584ec80000
kernel config: https://syzkaller.appspot.com/x/.config?x=d4215fb4040f8f8d
dashboard link: https://syzkaller.appspot.com/bug?extid=ec6d9a9ad2419bff5bb4
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/857e17de0f0a/disk-8020ae3c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9efc49fcd441/vmlinux-8020ae3c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f14c38b6bfa7/bzImage-8020ae3c.xz

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

INFO: task kworker/0:3:2180 blocked for more than 143 seconds.
Not tainted 5.15.103-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:3 state:D stack:23936 pid: 2180 ppid: 2 flags:0x00004000
Workqueue: events rfkill_sync_work
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0x1348/0x4610 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
device_lock include/linux/device.h:760 [inline]
nfc_dev_down net/nfc/core.c:143 [inline]
nfc_rfkill_set_block+0x4c/0x2f0 net/nfc/core.c:179
rfkill_set_block+0x1e7/0x430 net/rfkill/core.c:345
rfkill_sync_work+0x8a/0xe0 net/rfkill/core.c:1030
process_one_work+0x90d/0x1270 kernel/workqueue.c:2306
worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
INFO: task kworker/0:13:5673 blocked for more than 143 seconds.
Not tainted 5.15.103-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:13 state:D stack:18624 pid: 5673 ppid: 2 flags:0x00004000
Workqueue: events rfkill_global_led_trigger_worker
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0x1348/0x4610 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+0x90d/0x1270 kernel/workqueue.c:2306
worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
INFO: task syz-executor.0:18863 blocked for more than 143 seconds.
Not tainted 5.15.103-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack:27168 pid:18863 ppid: 3632 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5023 [inline]
__schedule+0x1348/0x4610 kernel/sched/core.c:6369
schedule+0x11b/0x1f0 kernel/sched/core.c:6452
schedule_timeout+0xac/0x300 kernel/time/timer.c:1860
do_wait_for_common+0x2d9/0x480 kernel/sched/completion.c:85
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x48/0x60 kernel/sched/completion.c:138
__flush_work+0x124/0x1a0 kernel/workqueue.c:3090
__cancel_work_timer+0x519/0x6a0 kernel/workqueue.c:3177
rfkill_unregister+0x92/0x220 net/rfkill/core.c:1112
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/0x2b0 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:0x7f799e66bfab
RSP: 002b:00007ffc8916ed10 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000005 RCX: 00007f799e66bfab
RDX: 0000000000000000 RSI: 0000001b2e320c70 RDI: 0000000000000004
RBP: 00007f799e7db980 R08: 0000000000000000 R09: 00000000b6ca338a
R10: 0000000000000000 R11: 0000000000000293 R12: 00000000000db603
R13: 00007ffc8916ee10 R14: 00007f799e7da050 R15: 0000000000000032
</TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c91c320 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
4 locks held by kworker/0:3/2180:
#0: ffff888011c64d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x794/0x1270 kernel/workqueue.c:2279
#1: ffffc90007e8fd20 ((work_completion)(&rfkill->sync_work)){+.+.}-{0:0}, at: process_one_work+0x7da/0x1270 kernel/workqueue.c:2281
#2: ffffffff8dc65ea8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_sync_work+0x25/0xe0 net/rfkill/core.c:1028
#3: ffff888082f53190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#3: ffff888082f53190 (&dev->mutex){....}-{3:3}, at: nfc_dev_down net/nfc/core.c:143 [inline]
#3: ffff888082f53190 (&dev->mutex){....}-{3:3}, at: nfc_rfkill_set_block+0x4c/0x2f0 net/nfc/core.c:179
2 locks held by getty/3268:
#0: ffff88814b1bf098 (&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/0:13/5673:
#0: ffff888011c64d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x794/0x1270 kernel/workqueue.c:2279
#1: ffffc900086afd20 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_one_work+0x7da/0x1270 kernel/workqueue.c:2281
#2: ffffffff8dc65ea8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_global_led_trigger_worker+0x23/0xd0 net/rfkill/core.c:181
2 locks held by kworker/u4:22/8660:
1 lock held by syz-executor.0/18863:
#0: ffff888082f53190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#0: ffff888082f53190 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x5f/0x290 net/nfc/core.c:1165
2 locks held by syz-executor.0/19134:
#0: ffff88807eda8918 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x34/0x590 drivers/bluetooth/hci_vhci.c:149
#1: ffffffff8dc65ea8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x30/0x880 net/rfkill/core.c:1045
2 locks held by syz-executor.0/19140:
#0: ffff88801bec9118 (&data->open_mutex){+.+.}-{3:3}, at: vhci_create_device+0x34/0x590 drivers/bluetooth/hci_vhci.c:149
#1: ffffffff8dc65ea8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_register+0x30/0x880 net/rfkill/core.c:1045

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

NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted 5.15.103-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+0xf54/0xfa0 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 8660 Comm: kworker/u4:22 Not tainted 5.15.103-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: bat_events batadv_nc_worker
RIP: 0010:preempt_count arch/x86/include/asm/preempt.h:27 [inline]
RIP: 0010:check_preemption_disabled+0x20/0x110 lib/smp_processor_id.c:16
Code: 8a 48 c7 c6 20 b9 d8 8a eb 00 41 57 41 56 41 54 53 48 83 ec 10 65 48 8b 04 25 28 00 00 00 48 89 44 24 08 65 8b 1d c0 27 df 75 <65> 8b 05 31 82 df 75 a9 ff ff ff 7f 74 22 65 48 8b 04 25 28 00 00
RSP: 0018:ffffc90005cdfa88 EFLAGS: 00000086
RAX: 9c49acf950d61100 RBX: 0000000000000000 RCX: 0000000080000001
RDX: 0000000000000000 RSI: ffffffff8a8b0a80 RDI: ffffffff8ad8b940
RBP: ffffc90005cdfbe8 R08: dffffc0000000000 R09: fffffbfff1bc7116
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff92000b9bf64
R13: 0000000000000246 R14: ffffc90005cdfb70 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c00dc7bc60 CR3: 000000001e846000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
lockdep_recursion_inc kernel/locking/lockdep.c:431 [inline]
lock_release+0x1a2/0x9d0 kernel/locking/lockdep.c:5641
rcu_read_unlock include/linux/rcupdate.h:729 [inline]
batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:416 [inline]
batadv_nc_worker+0x239/0x5b0 net/batman-adv/network-coding.c:723
process_one_work+0x90d/0x1270 kernel/workqueue.c:2306
worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S: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]

syzbot has found a reproducer for the following issue on:

HEAD commit: d54cfc420586 Linux 5.15.120
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12eb34caa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=61785ceccc6bdf75

dashboard link: https://syzkaller.appspot.com/bug?extid=ec6d9a9ad2419bff5bb4
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11d13d22a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=120d91b0a80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/df6c88d1a764/disk-d54cfc42.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/787a9f4e718c/vmlinux-d54cfc42.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4a60832537ff/Image-d54cfc42.gz.xz

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

INFO: task kworker/1:1:25 blocked for more than 143 seconds.
Not tainted 5.15.120-syzkaller #0

"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:kworker/1:1 state:D stack: 0 pid: 25 ppid: 2 flags:0x00000008
Workqueue: events rfkill_op_handler
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_epo+0x8c/0x158 net/rfkill/core.c:454
__rfkill_handle_global_op net/rfkill/input.c:60 [inline]
rfkill_op_handler+0x170/0x288 net/rfkill/input.c:108
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 kworker/1:4:4038 blocked for more than 143 seconds.
Not tainted 5.15.120-syzkaller #0

"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:kworker/1:4 state:D stack: 0 pid: 4038 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-executor142:7825 blocked for more than 143 seconds.
Not tainted 5.15.120-syzkaller #0

"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz-executor142 state:D stack: 0 pid: 7825 ppid: 3990 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

Showing all locks held in the system:

1 lock held by kdevtmpfs/23:
#0: ffff0001b480bd18 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested kernel/sched/core.c:475 [inline]
#0: ffff0001b480bd18 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock kernel/sched/sched.h:1326 [inline]
#0: ffff0001b480bd18 (&rq->__lock){-.-.}-{2:2}, at: rq_lock kernel/sched/sched.h:1621 [inline]
#0: ffff0001b480bd18 (&rq->__lock){-.-.}-{2:2}, at: __schedule+0x328/0x1e38 kernel/sched/core.c:6286
4 locks held by kworker/1:1/25:
#0: ffff0000c0020d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2280
#1: ffff800018a17c00 ((rfkill_op_work).work){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2282
#2: ffff800016c5ad48 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_epo+0x58/0x158 net/rfkill/core.c:450
#3: ffff0000cec9b190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#3: ffff0000cec9b190 (&dev->mutex){....}-{3:3}, at: nfc_dev_down net/nfc/core.c:143 [inline]
#3: ffff0000cec9b190 (&dev->mutex){....}-{3:3}, at: nfc_rfkill_set_block+0x50/0x2d0 net/nfc/core.c:179

1 lock held by khungtaskd/27:

#0: ffff800014ac19a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:268
2 locks held by getty/3723:
#0: ffff0000d3be0098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
#1: ffff80001a29b2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1200 drivers/tty/n_tty.c:2147
3 locks held by kworker/1:4/4038:
#0: ffff0000c0020d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2280
#1: ffff80001cea7c00 ((work_completion)(&rfkill_global_led_trigger_work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2282
#2: ffff800016c5ad48 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_global_led_trigger_worker+0x30/0xe4 net/rfkill/core.c:181
2 locks held by syz-executor142/7825:
#0: ffff0000cec9b190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#0: ffff0000cec9b190 (&dev->mutex){....}-{3:3}, at: nfc_unregister_device+0x6c/0x290 net/nfc/core.c:1165
#1: ffff800016c5ad48 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_unregister+0xb8/0x210 net/rfkill/core.c:1118
1 lock held by syz-executor142/10260:
#0: ffff8000161a1248 (input_mutex){+.+.}-{3:3}, at: __input_unregister_device+0x10c/0x304 drivers/input/input.c:2205
1 lock held by syz-executor142/10262:
#0: ffff8000161a1248 (input_mutex){+.+.}-{3:3}, at: __input_unregister_device+0x10c/0x304 drivers/input/input.c:2205
2 locks held by syz-executor142/10263:
#0: ffff0000d2a41870 (&newdev->mutex){+.+.}-{3:3}, at: uinput_ioctl_handler+0xf8/0x14b0 drivers/input/misc/uinput.c:851
#1: ffff8000161a1248 (input_mutex){+.+.}-{3:3}, at: input_register_device+0x924/0xe4c drivers/input/input.c:2347
2 locks held by syz-executor142/10264:
#0: ffff0000c5f14070 (&newdev->mutex){+.+.}-{3:3}, at: uinput_ioctl_handler+0xf8/0x14b0 drivers/input/misc/uinput.c:851
#1: ffff8000161a1248 (input_mutex){+.+.}-{3:3}, at: input_register_device+0x924/0xe4c drivers/input/input.c:2347
2 locks held by syz-executor142/10265:
#0: ffff0000d5335070 (&newdev->mutex){+.+.}-{3:3}, at: uinput_ioctl_handler+0xf8/0x14b0 drivers/input/misc/uinput.c:851
#1: ffff8000161a1248 (input_mutex){+.+.}-{3:3}, at: input_register_device+0x924/0xe4c drivers/input/input.c:2347

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



---
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.