[syzbot] [mm?] [ntfs3?] kernel panic: stack is corrupted in _raw_spin_unlock_irqrestore

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

syzbot found the following issue on:

HEAD commit:    e477dba5442c Merge tag 'for-6.12/dm-changes' of git://git...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14a8fa80580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b2d4fdf18a83ec0b
dashboard link: https://syzkaller.appspot.com/bug?extid=7614fef79a88d3c02bf2
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=101386a9980000

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-e477dba5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3bf119f19bb7/vmlinux-e477dba5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2de4db7684f9/bzImage-e477dba5.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/184157d9745b/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7614fef79a88d3c02bf2@xxxxxxxxxxxxxxxxxxxxxxxxx

loop0: detected capacity change from 0 to 256
exFAT-fs (loop0): failed to load upcase table (idx : 0x000104d0, chksum : 0x60d18cac, utbl_chksum : 0xe619d30d)
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: _raw_spin_unlock_irqrestore+0x137/0x140
CPU: 0 UID: 0 PID: 7456 Comm: syz.0.1047 Not tainted 6.11.0-syzkaller-11624-ge477dba5442c #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 panic+0x349/0x880 kernel/panic.c:354
 __stack_chk_fail+0x15/0x20 kernel/panic.c:836
 _raw_spin_unlock_irqrestore+0x137/0x140
 debug_object_activate+0x3e4/0x510 lib/debugobjects.c:726
 debug_rcu_head_queue kernel/rcu/rcu.h:224 [inline]
 __call_rcu_common kernel/rcu/tree.c:3071 [inline]
 call_rcu+0x97/0xa70 kernel/rcu/tree.c:3190
 slab_free_hook mm/slub.c:2307 [inline]
 slab_free mm/slub.c:4580 [inline]
 kmem_cache_free+0x2fc/0x420 mm/slub.c:4682
 anon_vma_free mm/rmap.c:138 [inline]
 __put_anon_vma+0x128/0x2d0 mm/rmap.c:2560
 put_anon_vma include/linux/rmap.h:116 [inline]
 unlink_anon_vmas+0x492/0x5f0 mm/rmap.c:445
 free_pgtables+0x567/0x840 mm/memory.c:409
 exit_mmap+0x48e/0xc40 mm/mmap.c:1875
 __mmput+0x115/0x390 kernel/fork.c:1347
 exit_mm+0x220/0x310 kernel/exit.c:571
 do_exit+0x9b2/0x28e0 kernel/exit.c:926
 do_group_exit+0x207/0x2c0 kernel/exit.c:1088
 get_signal+0x16a3/0x1740 kernel/signal.c:2917
 arch_do_signal_or_restart+0x96/0x860 arch/x86/kernel/signal.c:337
 exit_to_user_mode_loop kernel/entry/common.c:111 [inline]
 exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
 __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
 syscall_exit_to_user_mode+0xc9/0x370 kernel/entry/common.c:218
 do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fed97b7df39
Code: Unable to access opcode bytes at 0x7fed97b7df0f.
RSP: 002b:00007fed975ff0e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: 0000000000000001 RBX: 00007fed97d35f88 RCX: 00007fed97b7df39
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 00007fed97d35f8c
RBP: 00007fed97d35f80 R08: 7fffffffffffffff R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fed97d35f8c
R13: 0000000000000000 R14: 00007fff93524ba0 R15: 00007fff93524c88
 </TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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 syzkaller@xxxxxxxxxxxxxxxx.

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

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




[Index of Archives]     [Linux Driver Backports]     [DMA Engine]     [Linux GPIO]     [Linux SPI]     [Video for Linux]     [Linux USB Devel]     [Linux Coverity]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux