[v5.15] BUG: soft lockup in sys_execve

2 views
Skip to first unread message

syzbot

unread,
Nov 7, 2024, 4:26:20 PM11/7/24
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 72244eab0dad Linux 5.15.170
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16c26e30580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d85ac7994f3a5f02
dashboard link: https://syzkaller.appspot.com/bug?extid=5303991e287c7e10033b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a97549f813ef/disk-72244eab.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/399cdfbc4562/vmlinux-72244eab.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a7c1fce94960/Image-72244eab.gz.xz

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

watchdog: BUG: soft lockup - CPU#0 stuck for 24s! [dhcpcd-run-hook:8127]
Modules linked in:
irq event stamp: 560
hardirqs last enabled at (559): [<ffff800008917b04>] lock_page_memcg+0x11c/0x244 mm/memcontrol.c:2056
hardirqs last disabled at (560): [<ffff800011ab8cf4>] enter_el1_irq_or_nmi+0x10/0x1c arch/arm64/kernel/entry-common.c:227
softirqs last enabled at (20): [<ffff8000080308b0>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (18): [<ffff80000803087c>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
CPU: 0 PID: 8127 Comm: dhcpcd-run-hook Not tainted 5.15.170-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : lock_release+0x504/0xa1c
lr : lockdep_recursion_finish kernel/locking/lockdep.c:436 [inline]
lr : lock_release+0x4c4/0xa1c kernel/locking/lockdep.c:5645
sp : ffff800020a170a0
x29: ffff800020a17170 x28: ffff0000e7909b40 x27: dfff800000000000
x26: 0000000000000002 x25: ffff0000e790a570 x24: 00000000fff40219
x23: ffff0000e790a518 x22: 1fffe0001cf214a3 x21: e94a630af29398e7
x20: 0000000000000002 x19: ffff0001b418dd00 x18: 0000000000000001
x17: 0000000000000000 x16: ffff800011aba7a8 x15: 0000000000000005
x14: 1ffff0000295806a x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000000001 x10: 0000000000000003 x9 : 0000000000000080
x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000000 x3 : ffff8000087dc500
x2 : 0000000000000022 x1 : ffff800011c0bfc0 x0 : 0000000000000000
Call trace:
arch_local_irq_restore arch/arm64/include/asm/irqflags.h:122 [inline]
lock_release+0x504/0xa1c kernel/locking/lockdep.c:5646
__raw_spin_unlock include/linux/spinlock_api_smp.h:150 [inline]
_raw_spin_unlock+0x90/0x128 kernel/locking/spinlock.c:186
spin_unlock include/linux/spinlock.h:403 [inline]
zap_pte_range mm/memory.c:1435 [inline]
zap_pmd_range mm/memory.c:1494 [inline]
zap_pud_range mm/memory.c:1523 [inline]
zap_p4d_range mm/memory.c:1544 [inline]
unmap_page_range+0x16c8/0x19d4 mm/memory.c:1565
unmap_single_vma+0x13c/0x1e4 mm/memory.c:1610
unmap_vmas+0x1ac/0x320 mm/memory.c:1642
exit_mmap+0x2c8/0x558 mm/mmap.c:3186
__mmput+0xec/0x3b8 kernel/fork.c:1126
mmput+0x80/0xc8 kernel/fork.c:1147
exec_mmap+0x3e8/0x4d0 fs/exec.c:1035
begin_new_exec+0x6d0/0xee4 fs/exec.c:1293
load_elf_binary+0x73c/0x21a0 fs/binfmt_elf.c:1001
search_binary_handler fs/exec.c:1742 [inline]
exec_binprm fs/exec.c:1783 [inline]
bprm_execve+0x7f4/0x1578 fs/exec.c:1852
do_execveat_common+0x668/0x814 fs/exec.c:1957
do_execve fs/exec.c:2027 [inline]
__do_sys_execve fs/exec.c:2103 [inline]
__se_sys_execve fs/exec.c:2098 [inline]
__arm64_sys_execve+0x98/0xb0 fs/exec.c:2098
__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:608
el0t_64_sync_handler+0x84/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

unread,
Feb 15, 2025, 4:26:17 PM2/15/25
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages