[v6.1] BUG: soft lockup in smp_call_function

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7eaef76fbc46 Linux 6.1.20
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=131d43e2c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=28c36fe4d02f8c88
dashboard link: https://syzkaller.appspot.com/bug?extid=404835f31926b466eadd
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/610a00ba4375/disk-7eaef76f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/57c1310f9a30/vmlinux-7eaef76f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/81999f717d3b/bzImage-7eaef76f.xz

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

watchdog: BUG: soft lockup - CPU#1 stuck for 143s! [kworker/u4:17:4659]
Modules linked in:
irq event stamp: 4333376
hardirqs last enabled at (4333375): [<ffffffff8aa00cc6>] asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:649
hardirqs last disabled at (4333376): [<ffffffff8a8a405a>] sysvec_apic_timer_interrupt+0xa/0xb0 arch/x86/kernel/apic/apic.c:1107
softirqs last enabled at (4302624): [<ffffffff81543b15>] invoke_softirq kernel/softirq.c:445 [inline]
softirqs last enabled at (4302624): [<ffffffff81543b15>] __irq_exit_rcu+0x155/0x240 kernel/softirq.c:650
softirqs last disabled at (4302587): [<ffffffff81543b15>] invoke_softirq kernel/softirq.c:445 [inline]
softirqs last disabled at (4302587): [<ffffffff81543b15>] __irq_exit_rcu+0x155/0x240 kernel/softirq.c:650
CPU: 1 PID: 4659 Comm: kworker/u4:17 Not tainted 6.1.20-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:csd_lock_wait kernel/smp.c:413 [inline]
RIP: 0010:smp_call_function_many_cond+0x1f62/0x33d0 kernel/smp.c:987
Code: 2f 44 89 ee 83 e6 01 31 ff e8 7a 09 0b 00 41 83 e5 01 49 bd 00 00 00 00 00 fc ff df 75 0a e8 05 06 0b 00 e9 1b ff ff ff f3 90 <42> 0f b6 04 2b 84 c0 75 14 41 f7 07 01 00 00 00 0f 84 fe fe ff ff
RSP: 0018:ffffc90014fff5a0 EFLAGS: 00000293
RAX: ffffffff817f5b3d RBX: 1ffff11017308415 RCX: ffff8880300cd7c0
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc90014fff980 R08: ffffffff817f5b06 R09: fffffbfff204d831
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000800000000
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff8880b98420a8
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555569d6848 CR3: 000000000cc8e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
on_each_cpu_cond_mask+0x3b/0x80 kernel/smp.c:1155
on_each_cpu include/linux/smp.h:71 [inline]
text_poke_sync arch/x86/kernel/alternative.c:1316 [inline]
text_poke_bp_batch+0x2bb/0x940 arch/x86/kernel/alternative.c:1516
text_poke_flush arch/x86/kernel/alternative.c:1707 [inline]
text_poke_finish+0x16/0x30 arch/x86/kernel/alternative.c:1714
arch_jump_label_transform_apply+0x13/0x20 arch/x86/kernel/jump_label.c:146
static_key_enable_cpuslocked+0x12e/0x250 kernel/jump_label.c:177
static_key_enable+0x16/0x20 kernel/jump_label.c:190
toggle_allocation_gate+0xbf/0x480 mm/kfence/core.c:800
process_one_work+0x909/0x1380 kernel/workqueue.c:2289
worker_thread+0xa5f/0x1210 kernel/workqueue.c:2436
kthread+0x268/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 3764 Comm: syz-fuzzer Not tainted 6.1.20-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:__rcu_read_lock+0x0/0xb0 kernel/rcu/tree_plugin.h:399
Code: 39 fb ff ff 44 89 f1 80 e1 07 38 c1 0f 8c 2b fd ff ff 4c 89 f7 e8 f0 9f 6c 00 e9 1e fd ff ff e8 66 28 16 09 66 0f 1f 44 00 00 <55> 41 57 41 56 53 49 be 00 00 00 00 00 fc ff df 65 4c 8b 3d 88 49
RSP: 0000:ffffc90000007cb8 EFLAGS: 00000046
RAX: 1ffff11005cc5c6c RBX: ffff888058b9ec20 RCX: 0000000000010002
RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffff88802e62e358
RBP: ffff88802e62e2e8 R08: dffffc0000000000 R09: ffffed1005cc5c5e
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88802e62e000
R13: ffff88802e62e360 R14: dffffc0000000000 R15: 188174f1b102e9e3
FS: 000000c01b2cc490(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c014ac9f40 CR3: 000000007df52000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
rcu_read_lock include/linux/rcupdate.h:745 [inline]
advance_sched+0x6c9/0x940 net/sched/sch_taprio.c:753
__run_hrtimer kernel/time/hrtimer.c:1685 [inline]
__hrtimer_run_queues+0x670/0x1020 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1096 [inline]
__sysvec_apic_timer_interrupt+0x198/0x680 arch/x86/kernel/apic/apic.c:1113
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1107
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:649
RIP: 0010:debug_lockdep_rcu_enabled+0x25/0x30 kernel/rcu/update.c:281
Code: cc cc cc cc cc 31 c0 83 3d b7 9a c8 03 00 74 1d 83 3d 42 ce c8 03 00 74 14 65 48 8b 0d 54 1b 78 75 31 c0 83 b9 4c 0a 00 00 00 <0f> 94 c0 c3 cc cc cc cc cc cc cc 53 48 8b 7c 24 08 e8 55 fb ff ff
RSP: 0000:ffffc90005287638 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 1ffff92000a50ec8 RCX: ffff888078c11d40
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8e52ed68
RBP: ffffc900052876d0 R08: dffffc0000000000 R09: fffffbfff1ca5dae
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff92000a50ee8
R13: ffffffff81e2a4b5 R14: dffffc0000000000 R15: dffffc0000000000
rcu_read_lock_held_common kernel/rcu/update.c:104 [inline]
rcu_read_lock_sched_held+0x5f/0x130 kernel/rcu/update.c:123
trace_lock_release include/trace/events/lock.h:69 [inline]
lock_release+0x10b/0xab0 kernel/locking/lockdep.c:5680
rcu_read_unlock include/linux/rcupdate.h:780 [inline]
node_is_toptier+0x212/0x270 mm/memory-tiers.c:263
task_numa_fault+0x137/0x4930 kernel/sched/fair.c:2844
do_numa_page mm/memory.c:4794 [inline]
handle_pte_fault mm/memory.c:4957 [inline]
__handle_mm_fault mm/memory.c:5092 [inline]
handle_mm_fault+0x31c2/0x5140 mm/memory.c:5213
do_user_addr_fault arch/x86/mm/fault.c:1428 [inline]
handle_page_fault arch/x86/mm/fault.c:1519 [inline]
exc_page_fault+0x655/0x860 arch/x86/mm/fault.c:1575
asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:0x41f64b
Code: 85 c9 75 20 4c 89 44 24 38 e8 f1 55 ff ff 48 85 f6 0f 84 97 00 00 00 48 8b 54 24 78 49 89 f1 48 8b 74 24 48 4d 89 c8 49 29 d0 <4d> 8b 09 4d 85 c9 74 b1 4d 89 ca 49 29 d1 4c 39 ce 77 a6 4c 89 44
RSP: 002b:000000c001761e88 EFLAGS: 00010202
RAX: 000000c014ac9f20 RBX: 0000000000000030 RCX: 0000000000000000
RDX: 000000c014ac9f20 RSI: 0000000000000030 RDI: 0000000000000006
RBP: 000000c001761f08 R08: 0000000000000020 R09: 000000c014ac9f40
R10: 0000000000000010 R11: 000000000000003e R12: 000000c001761f08
R13: 0000000000000000 R14: 000000c000644d00 R15: 0000000000000001
</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]

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=16eb98a1c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=d4215fb4040f8f8d
dashboard link: https://syzkaller.appspot.com/bug?extid=f61e8f4a149eefab5677

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+f61e8f...@syzkaller.appspotmail.com

watchdog: BUG: soft lockup - CPU#0 stuck for 143s! [syz-executor.4:3717]
Modules linked in:
irq event stamp: 29340
hardirqs last enabled at (29339): [<ffffffff8a400cc6>] asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:638
hardirqs last disabled at (29340): [<ffffffff8a22cbaa>] sysvec_apic_timer_interrupt+0xa/0xb0 arch/x86/kernel/apic/apic.c:1097
softirqs last enabled at (484): [<ffffffff814d9505>] invoke_softirq kernel/softirq.c:432 [inline]
softirqs last enabled at (484): [<ffffffff814d9505>] __irq_exit_rcu+0x155/0x240 kernel/softirq.c:636
softirqs last disabled at (415): [<ffffffff814d9505>] invoke_softirq kernel/softirq.c:432 [inline]
softirqs last disabled at (415): [<ffffffff814d9505>] __irq_exit_rcu+0x155/0x240 kernel/softirq.c:636
CPU: 0 PID: 3717 Comm: syz-executor.4 Not tainted 5.15.103-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023

RIP: 0010:csd_lock_wait kernel/smp.c:440 [inline]
RIP: 0010:smp_call_function_many_cond+0xa93/0xd90 kernel/smp.c:969
Code: 04 03 84 c0 0f 85 84 00 00 00 45 8b 7d 00 44 89 fe 83 e6 01 31 ff e8 0c bf 0b 00 41 83 e7 01 75 07 e8 a1 bb 0b 00 eb 41 f3 90 <48> b8 00 00 00 00 00 fc ff df 0f b6 04 03 84 c0 75 11 41 f7 45 00
RSP: 0018:ffffc9000309f220 EFLAGS: 00000246
RAX: ffffffff8174bd54 RBX: 1ffff11017367f19 RCX: 0000000000040000
RDX: ffffc900038b5000 RSI: 000000000003ffff RDI: 0000000000040000
RBP: ffffc9000309f360 R08: ffffffff8174bd24 R09: fffffbfff1f76615
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000001
R13: ffff8880b9b3f8c8 R14: ffff8880b9a3a700 R15: 0000000000000001
FS: 00007fa621b91700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007fa623740988 CR3: 00000000786c1000 CR4: 00000000003506f0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:

<TASK>
on_each_cpu_cond_mask+0x3b/0x80 kernel/smp.c:1135
__purge_vmap_area_lazy+0x294/0x1740 mm/vmalloc.c:1683
_vm_unmap_aliases+0x453/0x4e0 mm/vmalloc.c:2107
change_page_attr_set_clr+0x308/0x1050 arch/x86/mm/pat/set_memory.c:1740
change_page_attr_clear arch/x86/mm/pat/set_memory.c:1797 [inline]
set_memory_ro+0xa1/0xe0 arch/x86/mm/pat/set_memory.c:1943
bpf_jit_binary_lock_ro include/linux/filter.h:888 [inline]
bpf_int_jit_compile+0xbf57/0xc6e0 arch/x86/net/bpf_jit_comp.c:2372
bpf_prog_select_runtime+0x6e2/0x9b0 kernel/bpf/core.c:1926
bpf_prog_load+0x131c/0x1b60 kernel/bpf/syscall.c:2329
__sys_bpf+0x343/0x670 kernel/bpf/syscall.c:4614
__do_sys_bpf kernel/bpf/syscall.c:4718 [inline]
__se_sys_bpf kernel/bpf/syscall.c:4716 [inline]
__x64_sys_bpf+0x78/0x90 kernel/bpf/syscall.c:4716
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fa62361f0f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fa621b91168 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 00007fa62373ef80 RCX: 00007fa62361f0f9
RDX: 0000000000000080 RSI: 00000000200004c0 RDI: 0000000000000005
RBP: 00007fa62367ab39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffea7587aaf R14: 00007fa621b91300 R15: 0000000000022000
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 3712 Comm: syz-executor.5 Not tainted 5.15.103-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023

RIP: 0010:lock_is_held_type+0x11b/0x180 kernel/locking/lockdep.c:5667
Code: 48 c7 c7 20 0f 8b 8a e8 43 12 00 00 b8 ff ff ff ff 65 0f c1 05 b6 9c df 75 83 f8 01 75 40 48 c7 04 24 00 00 00 00 9c 8f 04 24 <f7> 04 24 00 02 00 00 75 46 41 f7 c4 00 02 00 00 74 01 fb 65 48 8b
RSP: 0018:ffffc90000dd0c78 EFLAGS: 00000046
RAX: 0000000000000001 RBX: 1ffff920001ba198 RCX: 0000000000010002
RDX: ffff8880a1fed700 RSI: ffffffff8a8b0f20 RDI: ffffffff8ad8b940
RBP: 0000000000000000 R08: ffffffff816f916a R09: fffffbfff1bc7116
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000046
R13: ffff8880a1fed700 R14: 00000000ffffffff R15: ffffffff8c91c2a0
FS: 00005555559ed400(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007f80d3396000 CR3: 00000000824cd000 CR4: 00000000003506e0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:

<IRQ>
lock_is_held include/linux/lockdep.h:287 [inline]
rcu_read_lock_sched_held+0x89/0x130 kernel/rcu/update.c:125
trace_hrtimer_expire_entry include/trace/events/timer.h:232 [inline]
__run_hrtimer kernel/time/hrtimer.c:1682 [inline]
__hrtimer_run_queues+0x543/0xeb0 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1086 [inline]
__sysvec_apic_timer_interrupt+0x17b/0x570 arch/x86/kernel/apic/apic.c:1103
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1097
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:638
RIP: 0010:__raw_spin_unlock_irq include/linux/spinlock_api_smp.h:169 [inline]
RIP: 0010:_raw_spin_unlock_irq+0x25/0x40 kernel/locking/spinlock.c:202
Code: 81 a9 f6 ff 90 53 48 89 fb 48 83 c7 18 48 8b 74 24 08 e8 1e bb 36 f7 48 89 df e8 e6 0d 38 f7 e8 e1 b8 5a f7 fb bf 01 00 00 00 <e8> b6 43 2b f7 65 8b 05 37 40 d6 75 85 c0 74 02 5b c3 e8 64 5a d4
RSP: 0018:ffffc90002c5fec0 EFLAGS: 00000282
RAX: a64ee39ddba08800 RBX: ffff8880874cc0c0 RCX: ffffffff913aaf03
RDX: dffffc0000000000 RSI: ffffffff8a8afc80 RDI: 0000000000000001
RBP: dffffc0000000000 R08: ffffffff8186e890 R09: ffffed1010e99819
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: 1ffff1100fa930e4 R14: ffff8880874cc0c0 R15: 1ffff1100fa930e5
spin_unlock_irq include/linux/spinlock.h:413 [inline]
do_group_exit+0x254/0x310 kernel/exit.c:991
__do_sys_exit_group kernel/exit.c:1005 [inline]
__se_sys_exit_group kernel/exit.c:1003 [inline]
__x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1003
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f80d327a0f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc6349b908 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 000000000000001e RCX: 00007f80d327a0f9
RDX: 00007f80d322bfab RSI: ffffffffffffffb8 RDI: 0000000000000000
RBP: 0000000000000000 R08: 00007f80d2dee000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000001 R15: 00007ffc6349b9f0

[syzbot]

> #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux

This crash does not have a reproducer. I cannot test it.

> master

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: f67653019430 Linux 5.15.118
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13df97b7280000
kernel config: https://syzkaller.appspot.com/x/.config?x=c6daef03436a2bc5

dashboard link: https://syzkaller.appspot.com/bug?extid=f61e8f4a149eefab5677
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=14136a00a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17c1201b280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/600ef9372d32/disk-f6765301.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/46dca37198b3/vmlinux-f6765301.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7ae4a35a0a6d/Image-f6765301.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/9ca40e1d20fd/mount_7.gz

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

watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [syz-executor247:4047]
Modules linked in:
irq event stamp: 9390
hardirqs last enabled at (9389): [<ffff800011952c58>] __exit_to_kernel_mode arch/arm64/kernel/entry-common.c:81 [inline]
hardirqs last enabled at (9389): [<ffff800011952c58>] exit_to_kernel_mode+0x100/0x178 arch/arm64/kernel/entry-common.c:91
hardirqs last disabled at (9390): [<ffff800011952ea0>] enter_el1_irq_or_nmi+0x10/0x1c arch/arm64/kernel/entry-common.c:227
softirqs last enabled at (4938): [<ffff800008020ccc>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (4938): [<ffff800008020ccc>] __do_softirq+0xb5c/0xe20 kernel/softirq.c:587
softirqs last disabled at (4753): [<ffff8000081b573c>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (4753): [<ffff8000081b573c>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (4753): [<ffff8000081b573c>] __irq_exit_rcu+0x28c/0x534 kernel/softirq.c:636
CPU: 1 PID: 4047 Comm: syz-executor247 Not tainted 5.15.118-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : csd_lock_wait kernel/smp.c:440 [inline]
pc : smp_call_function_many_cond+0xa50/0x1088 kernel/smp.c:969
lr : csd_lock_wait kernel/smp.c:440 [inline]
lr : smp_call_function_many_cond+0xa68/0x1088 kernel/smp.c:969
sp : ffff80001d047900
x29: ffff80001d047950 x28: ffff0001b482cd48 x27: dfff800000000000
x26: 0000000000000011 x25: ffff0001b482cd40 x24: ffff8000148f0ff8
x23: 1fffe000369059a8 x22: ffff0001b48131c8 x21: ffff800014adda40
x20: 0000000000000000 x19: ffff0001b482cd48 x18: ffff80001d047620
x17: 0000000000000000 x16: ffff8000119547c4 x15: 0000000000011af3
x14: 1ffff0000291e06a x13: ffffffffffffffff x12: 0000000000000000
x11: ff8080000840ef98 x10: 0000000000000000 x9 : 0000000000000000
x8 : 0000000000000011 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000000 x3 : ffff80000840ef8c
x2 : 0000000000000000 x1 : 0000000000000004 x0 : 0000000000000001
Call trace:
__cmpwait_case_32 arch/arm64/include/asm/cmpxchg.h:252 [inline]
__cmpwait arch/arm64/include/asm/cmpxchg.h:278 [inline]
csd_lock_wait kernel/smp.c:440 [inline]
smp_call_function_many_cond+0xa50/0x1088 kernel/smp.c:969
smp_call_function_many+0x40/0x54 kernel/smp.c:993
clock_was_set+0x69c/0x784 kernel/time/hrtimer.c:974
do_settimeofday64+0x6e0/0x8f0 kernel/time/timekeeping.c:1328
do_sys_settimeofday64+0x1b8/0x23c kernel/time/time.c:195
posix_clock_realtime_set+0x24/0x34 kernel/time/posix-timers.c:185
__do_sys_clock_settime kernel/time/posix-timers.c:1092 [inline]
__se_sys_clock_settime kernel/time/posix-timers.c:1080 [inline]
__arm64_sys_clock_settime+0x1fc/0x248 kernel/time/posix-timers.c:1080
__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


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