[v5.15] BUG: soft lockup in sys_getsockopt

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 98f47d0e9b8c Linux 5.15.184
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10f0c570580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9eb2b5a65dfc4761
dashboard link: https://syzkaller.appspot.com/bug?extid=206892fc06f0412520ed
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d2845fb3af6c/disk-98f47d0e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1f12b743be24/vmlinux-98f47d0e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8f178b57ea38/Image-98f47d0e.gz.xz

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

watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [syz-executor:4029]
Modules linked in:
irq event stamp: 141912
hardirqs last enabled at (141911): [<ffff8000111a3bac>] __exit_to_kernel_mode arch/arm64/kernel/entry-common.c:81 [inline]
hardirqs last enabled at (141911): [<ffff8000111a3bac>] exit_to_kernel_mode+0xe0/0x168 arch/arm64/kernel/entry-common.c:91
hardirqs last disabled at (141912): [<ffff8000111a3e04>] enter_el1_irq_or_nmi+0x10/0x1c arch/arm64/kernel/entry-common.c:227
softirqs last enabled at (137536): [<ffff80000819d0d8>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (137536): [<ffff80000819d0d8>] handle_softirqs+0xa4c/0xbf0 kernel/softirq.c:586
softirqs last disabled at (137483): [<ffff80000819d6dc>] __do_softirq kernel/softirq.c:592 [inline]
softirqs last disabled at (137483): [<ffff80000819d6dc>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (137483): [<ffff80000819d6dc>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (137483): [<ffff80000819d6dc>] __irq_exit_rcu+0x240/0x440 kernel/softirq.c:641
CPU: 0 PID: 4029 Comm: syz-executor Not tainted 5.15.184-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
pstate: 00400005 (nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : queued_spin_lock_slowpath+0x13c/0x798 kernel/locking/qspinlock.c:382
lr : queued_spin_lock_slowpath+0x148/0x798 kernel/locking/qspinlock.c:382
sp : ffff80001f1b6b60
x29: ffff80001f1b6c00 x28: ffff8000140a1008 x27: 1ffff0000287a7bd
x26: 0000000000000001 x25: ffff0000e5e70000 x24: dfff800000000000
x23: ffff700003e36d70 x22: 1ffff00003e36d90 x21: ffff8000143d3de8
x20: ffff8000143d3df0 x19: ffff8000143d3de0 x18: 0000000000000000
x17: 0000000000000000 x16: ffff8000082d465c x15: 0000000000000000
x14: 00000000ffff8000 x13: 1ffff0000282a06b x12: 0000000000000001
x11: 1ffff0000287a7bc x10: 0000000000000000 x9 : 0000000000000000
x8 : 0000000000000101 x7 : ffff80000879c09c x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff8000082d3960
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]
queued_spin_lock_slowpath+0x13c/0x798 kernel/locking/qspinlock.c:382
queued_spin_lock include/asm-generic/qspinlock.h:85 [inline]
do_raw_spin_lock+0x2ec/0x2f0 kernel/locking/spinlock_debug.c:115
__raw_spin_lock include/linux/spinlock_api_smp.h:143 [inline]
_raw_spin_lock+0xb8/0x10c kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:363 [inline]
preload_this_cpu_lock mm/vmalloc.c:1500 [inline]
alloc_vmap_area+0x268/0x1698 mm/vmalloc.c:1542
__get_vm_area_node+0x17c/0x2e8 mm/vmalloc.c:2423
__vmalloc_node_range+0xe8/0x8d8 mm/vmalloc.c:3020
__vmalloc_node mm/vmalloc.c:3080 [inline]
vmalloc+0x118/0x190 mm/vmalloc.c:3113
ebt_register_table+0x1c0/0xd88 net/bridge/netfilter/ebtables.c:1206
frame_filter_table_init+0x30/0x40 net/bridge/netfilter/ebtable_filter.c:83
find_inlist_lock_noload+0x178/0x260 net/bridge/netfilter/ebtables.c:343
find_inlist_lock net/bridge/netfilter/ebtables.c:370 [inline]
find_table_lock net/bridge/netfilter/ebtables.c:379 [inline]
do_ebt_get_ctl+0x3fc/0x21ec net/bridge/netfilter/ebtables.c:2467
nf_getsockopt+0x264/0x284 net/netfilter/nf_sockopt.c:116
ip_getsockopt+0xffc/0x158c net/ipv4/ip_sockglue.c:1797
tcp_getsockopt+0x214/0x2e74 net/ipv4/tcp.c:4313
sock_common_getsockopt+0xa8/0xc4 net/core/sock.c:3418
__sys_getsockopt+0x1e0/0x45c net/socket.c:2247
__do_sys_getsockopt net/socket.c:2262 [inline]
__se_sys_getsockopt net/socket.c:2259 [inline]
__arm64_sys_getsockopt+0xb8/0xd4 net/socket.c:2259
__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+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584


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

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.