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: 486d, last: 28d
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 (7)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream kernel panic: stack is corrupted in __schedule (3) kernel 2 2 1099d 1108d 0/29 auto-obsoleted due to no activity on 2022/11/23 03:17
linux-6.1 kernel panic: stack is corrupted in __schedule 2 1 465d 465d 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) 2 4 226d 313d 0/3 auto-obsoleted due to no activity on 2025/04/24 00:04
upstream kernel panic: stack is corrupted in __schedule kernel 2 1 1830d 1826d 0/29 auto-closed as invalid on 2020/11/21 13:35
linux-6.1 kernel panic: stack is corrupted in __schedule (3) origin:upstream missing-backport 2 C 5 3d14h 109d 0/3 upstream: reported C repro on 2025/05/11 08:28
upstream kernel panic: stack is corrupted in __schedule (2) kernel 2 1 1369d 1365d 0/29 auto-closed as invalid on 2022/01/26 17:30
linux-6.6 kernel panic: stack is corrupted in __schedule 2 C 2 2d00h 71d 0/2 upstream: reported C repro on 2025/06/18 02:33
Last patch testing requests (10)
Created Duration User Patch Repo Result
2025/08/24 01:29 20m retest repro upstream OK log
2025/08/24 00:36 19m retest repro upstream OK log
2025/08/24 00:36 20m retest repro upstream OK log
2025/08/23 23:44 20m retest repro upstream OK log
2025/06/14 23:08 22m retest repro upstream report log
2025/06/14 23:08 22m retest repro upstream report log
2025/06/14 23:08 22m retest repro upstream report log
2025/06/14 23:08 21m retest repro upstream report log
2025/03/28 12:41 16m retest repro upstream error
2025/03/28 12:41 15m retest repro upstream error

Sample crash report:
loop1: detected capacity change from 0 to 4096
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __schedule+0x1abf/0x4ca0 kernel/sched/core.c:-1
CPU: 1 UID: 0 PID: 6729 Comm: syz.1.143 Tainted: G        W           6.16.0-syzkaller-04405-g4b290aae788e #0 PREEMPT_{RT,(full)} 
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x99/0x250 lib/dump_stack.c:120
 panic+0x2db/0x790 kernel/panic.c:442
 __stack_chk_fail+0x26/0x30 kernel/panic.c:929
 __schedule+0x1abf/0x4ca0 kernel/sched/core.c:-1
 preempt_schedule_irq+0xb5/0x150 kernel/sched/core.c:7281
 irqentry_exit+0x6f/0x90 kernel/entry/common.c:196
 asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:702
RIP: 0010:__sanitizer_cov_trace_const_cmp8+0x0/0xa0 kernel/kcov.c:320
Code: 00 00 48 89 7c 0a 10 48 89 74 0a 18 48 89 44 0a 20 c3 cc cc cc cc cc 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 <f3> 0f 1e fa 48 8b 04 24 65 48 8b 0c 25 08 e0 cf 91 65 44 8b 05 d7
RSP: 0018:ffffc90005f5f7f0 EFLAGS: 00000246
RAX: ffffffff81f82a44 RBX: ffffea0001901480 RCX: ffff888024fa8000
RDX: 0000000000000002 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 1ffffd4000320291 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff94000320291 R12: 0000000000000000
R13: 1ffffd4000320290 R14: ffffea0001901488 R15: 0000000000000000
 folio_mark_accessed+0x115/0x4a0 mm/swap.c:-1
 do_read_cache_folio+0x45d/0x560 mm/filemap.c:3932
 do_read_cache_page mm/filemap.c:3989 [inline]
 read_cache_page+0x5d/0x170 mm/filemap.c:3998
 read_mapping_page include/linux/pagemap.h:993 [inline]
 inode_read_data+0xa9/0x460 fs/ntfs3/inode.c:1054
 ntfs_fill_super+0x341c/0x40b0 fs/ntfs3/super.c:1482
 get_tree_bdev_flags+0x40b/0x4d0 fs/super.c:1692
 vfs_get_tree+0x92/0x2b0 fs/super.c:1815
 do_new_mount+0x2a2/0x9e0 fs/namespace.c:3805
 do_mount fs/namespace.c:4133 [inline]
 __do_sys_mount fs/namespace.c:4344 [inline]
 __se_sys_mount+0x317/0x410 fs/namespace.c:4321
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f545aff014a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f5458e55e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f5458e55ef0 RCX: 00007f545aff014a
RDX: 0000200000000280 RSI: 0000200000000300 RDI: 00007f5458e55eb0
RBP: 0000200000000280 R08: 00007f5458e55ef0 R09: 0000000000210802
R10: 0000000000210802 R11: 0000000000000246 R12: 0000200000000300
R13: 00007f5458e55eb0 R14: 000000000001f781 R15: 0000200000000840
 </TASK>
Kernel Offset: disabled
----------------
Code disassembly (best guess):
   0:	00 00                	add    %al,(%rax)
   2:	48 89 7c 0a 10       	mov    %rdi,0x10(%rdx,%rcx,1)
   7:	48 89 74 0a 18       	mov    %rsi,0x18(%rdx,%rcx,1)
   c:	48 89 44 0a 20       	mov    %rax,0x20(%rdx,%rcx,1)
  11:	c3                   	ret
  12:	cc                   	int3
  13:	cc                   	int3
  14:	cc                   	int3
  15:	cc                   	int3
  16:	cc                   	int3
  17:	0f 1f 00             	nopl   (%rax)
  1a:	90                   	nop
  1b:	90                   	nop
  1c:	90                   	nop
  1d:	90                   	nop
  1e:	90                   	nop
  1f:	90                   	nop
  20:	90                   	nop
  21:	90                   	nop
  22:	90                   	nop
  23:	90                   	nop
  24:	90                   	nop
  25:	90                   	nop
  26:	90                   	nop
  27:	90                   	nop
  28:	90                   	nop
  29:	90                   	nop
* 2a:	f3 0f 1e fa          	endbr64 <-- trapping instruction
  2e:	48 8b 04 24          	mov    (%rsp),%rax
  32:	65 48 8b 0c 25 08 e0 	mov    %gs:0xffffffff91cfe008,%rcx
  39:	cf 91
  3b:	65                   	gs
  3c:	44                   	rex.R
  3d:	8b                   	.byte 0x8b
  3e:	05                   	.byte 0x5
  3f:	d7                   	xlat   %ds:(%rbx)

Crashes (56):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/30 21:26 upstream 4b290aae788e f8f2b4da .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel panic: stack is corrupted in __schedule
2025/04/19 16:35 upstream 3088d26962e8 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root kernel panic: stack is corrupted in __schedule
2025/02/16 18:12 upstream ad1b832bf1cf 40a34ec9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-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/04/26 12:12 upstream f1a3944c860b c6b4fb39 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/03/14 11:42 upstream e3a854b577cb e2826670 .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/03/14 11:40 upstream e3a854b577cb e2826670 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/03/14 09:44 upstream e3a854b577cb e2826670 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/03/12 23:51 upstream 0fed89a961ea 1a5d9317 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/03/12 14:09 upstream 0fed89a961ea ee70e6db .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/03/12 02:45 upstream 0b46b049d6ec ee70e6db .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/03/10 13:17 upstream 80e54e84911a 16256247 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/03/09 17:22 upstream 1110ce6a1e34 163f510d .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/03/09 16:51 upstream 1110ce6a1e34 163f510d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/03/06 23:43 upstream f315296c92fd 831e3629 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/03/05 15:08 upstream 48a5eed9ad58 60f5d8d9 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel panic: stack is corrupted in __schedule
2025/02/19 22:07 upstream 6537cfb395f3 cbd8edab .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-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: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/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 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
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
2025/05/31 22:55 linux-next 3a83b350b5be 3d2f584d .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/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.