syzbot


kernel panic: stack is corrupted in __schedule (4)

Status: upstream: reported syz repro on 2024/08/20 16:14
Subsystems: ntfs3
[Documentation on labels]
Reported-by: syzbot+107a9ed6ac26198d4907@syzkaller.appspotmail.com
First crash: 293d, last: 1d01h
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [kernel?] kernel panic: stack is corrupted in __schedule (4) 0 (2) 2025/02/01 14:46
Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream kernel panic: stack is corrupted in __schedule (3) kernel 2 905d 915d 0/28 auto-obsoleted due to no activity on 2022/11/23 03:17
linux-6.1 kernel panic: stack is corrupted in __schedule 1 272d 272d 0/3 auto-obsoleted due to no activity on 2024/08/27 17:04
linux-6.1 kernel panic: stack is corrupted in __schedule (2) 4 33d 120d 0/3 upstream: reported on 2024/10/19 00:59
upstream kernel panic: stack is corrupted in __schedule kernel 1 1637d 1633d 0/28 auto-closed as invalid on 2020/11/21 13:35
upstream kernel panic: stack is corrupted in __schedule (2) kernel 1 1176d 1172d 0/28 auto-closed as invalid on 2022/01/26 17:30

Sample crash report:
loop0: detected capacity change from 0 to 4096
ntfs3(loop0): Different NTFS sector size (2048) and media sector size (512).
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __schedule+0x22fc/0x4c90
CPU: 0 UID: 0 PID: 6201 Comm: syz.0.287 Not tainted 6.14.0-rc1-syzkaller-00187-g8f6629c004b1 #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
 __schedule+0x22fc/0x4c90
 preempt_schedule_common+0x84/0xd0 kernel/sched/core.c:6943
 preempt_schedule+0xe1/0xf0 kernel/sched/core.c:6967
 preempt_schedule_thunk+0x1a/0x30 arch/x86/entry/thunk.S:12
 __raw_spin_unlock include/linux/spinlock_api_smp.h:143 [inline]
 _raw_spin_unlock+0x3e/0x50 kernel/locking/spinlock.c:186
 spin_unlock include/linux/spinlock.h:391 [inline]
 zap_pte_range mm/memory.c:1761 [inline]
 zap_pmd_range mm/memory.c:1823 [inline]
 zap_pud_range mm/memory.c:1852 [inline]
 zap_p4d_range mm/memory.c:1873 [inline]
 unmap_page_range+0x3d52/0x48d0 mm/memory.c:1894
 unmap_vmas+0x3cc/0x5f0 mm/memory.c:1984
 exit_mmap+0x283/0xd40 mm/mmap.c:1284
 __mmput+0x115/0x420 kernel/fork.c:1356
 exit_mm+0x220/0x310 kernel/exit.c:570
 do_exit+0x9ad/0x28e0 kernel/exit.c:925
 do_group_exit+0x207/0x2c0 kernel/exit.c:1087
 get_signal+0x16b2/0x1750 kernel/signal.c:3036
 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:329 [inline]
 __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
 syscall_exit_to_user_mode+0xce/0x340 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:0x7f3cf978cde9
Code: Unable to access opcode bytes at 0x7f3cf978cdbf.
RSP: 002b:00007f3cfa5970e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: 0000000000000001 RBX: 00007f3cf99a5fa8 RCX: 00007f3cf978cde9
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 00007f3cf99a5fac
RBP: 00007f3cf99a5fa0 R08: 7fffffffffffffff R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 00007f3cf99a5fac
R13: 0000000000000000 R14: 00007ffde0341880 R15: 00007ffde0341968
 </TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (39):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/02/08 21:39 upstream 8f6629c004b1 ef44b750 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/02/01 14:45 upstream 69e858e0b8b2 0dff8567 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2024/04/28 11:26 upstream 2c8159388952 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root kernel panic: stack is corrupted in __schedule
2025/02/15 00:35 upstream 04f41cbf03ec 40a34ec9 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/02/08 21:12 upstream 8f6629c004b1 ef44b750 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/02/02 12:25 upstream 69e858e0b8b2 568559e4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/02/02 10:13 upstream 69e858e0b8b2 568559e4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/02/01 13:17 upstream 69e858e0b8b2 0dff8567 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/01/22 17:01 upstream c4b9570cfb63 25e17fd3 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/01/21 17:04 upstream 95ec54a420b8 da72ac06 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/01/09 15:02 upstream eea6e4b4dfb8 9220929f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/01/08 04:09 upstream 09a0fa92e5b4 f3558dbf .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2024/12/16 23:07 upstream f44d154d6e3d f93b2b55 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2024/12/15 08:01 upstream 2d8308bf5b67 7cbfbb3a .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2024/12/11 23:38 upstream 231825b2e1ff 6f1b0fa8 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2024/11/11 17:29 upstream 2d5404caa8c7 0c4b1325 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2024/09/28 14:21 upstream ad46e8f95e93 ba29ff75 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2024/09/28 14:21 upstream ad46e8f95e93 ba29ff75 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2024/09/27 21:31 upstream e477dba5442c 2b1784d6 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2024/08/28 00:06 linux-next 6f923748057a 6c853ff9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/27 20:07 linux-next 6f923748057a 6c853ff9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/23 08:02 linux-next c79c85875f1a ce8a9099 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/23 07:28 linux-next c79c85875f1a ce8a9099 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/23 01:50 linux-next 6a7917c89f21 295a4b50 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/22 23:42 linux-next 6a7917c89f21 295a4b50 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/22 16:46 linux-next 6a7917c89f21 295a4b50 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/22 02:26 linux-next eb8c5ca373cb ca02180f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/22 01:26 linux-next eb8c5ca373cb ca02180f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/21 20:26 linux-next eb8c5ca373cb db5852f9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/21 19:26 linux-next eb8c5ca373cb db5852f9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/21 17:46 linux-next eb8c5ca373cb db5852f9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/21 08:51 linux-next eb8c5ca373cb 9f0ab3fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/21 04:20 linux-next bb1b0acdcd66 9f0ab3fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/20 23:18 linux-next bb1b0acdcd66 9f0ab3fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/20 21:24 linux-next bb1b0acdcd66 9f0ab3fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/20 16:13 linux-next bb1b0acdcd66 9f0ab3fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/08/20 09:32 linux-next bb1b0acdcd66 9f0ab3fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/07/24 15:22 linux-next 9ec6ec93f2c1 b24754ac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
2024/06/08 08:56 linux-next d35b2284e966 82c05ab8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root kernel panic: stack is corrupted in __schedule
* Struck through repros no longer work on HEAD.