syzbot


kernel panic: stack is corrupted in __schedule

Status: upstream: reported on 2024/05/19 17:04
Reported-by: syzbot+19e8e0a9e45f4dcd6b10@syzkaller.appspotmail.com
First crash: 26d, last: 26d
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream kernel panic: stack is corrupted in __schedule (3) kernel 2 659d 668d 0/27 auto-obsoleted due to no activity on 2022/11/23 03:17
upstream kernel panic: stack is corrupted in __schedule kernel 1 1391d 1387d 0/27 auto-closed as invalid on 2020/11/21 13:35
upstream kernel panic: stack is corrupted in __schedule (2) kernel 1 930d 926d 0/27 auto-closed as invalid on 2022/01/26 17:30
upstream kernel panic: stack is corrupted in __schedule (4) kernel 2 6d10h 43d 0/27 moderation: reported on 2024/05/02 11:28

Sample crash report:
loop1: detected capacity change from 0 to 4096
ntfs3: loop1: Different NTFS' sector size (1024) and media sector size (512)
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __schedule+0x203f/0x4550
CPU: 1 PID: 4019 Comm: syz-executor.1 Not tainted 6.1.91-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 panic+0x318/0x764 kernel/panic.c:339
 __stack_chk_fail+0x10/0x10 kernel/panic.c:767
 __schedule+0x203f/0x4550
 preempt_schedule_irq+0xf7/0x1c0 kernel/sched/core.c:6870
 irqentry_exit+0x53/0x80 kernel/entry/common.c:439
 asm_sysvec_reschedule_ipi+0x16/0x20 arch/x86/include/asm/idtentry.h:658
RIP: 0010:timespec64_compare include/linux/time64.h:63 [inline]
RIP: 0010:relatime_need_update fs/inode.c:1862 [inline]
RIP: 0010:atime_needs_update+0x557/0x7b0 fs/inode.c:1955
Code: 0f 11 92 ff eb 75 49 8d 7e 70 48 89 f8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df 80 3c 08 00 74 05 e8 6d 90 e9 ff 49 8b 6e 70 <49> 83 c6 60 4c 89 f0 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df 80
RSP: 0018:ffffc90005266858 EFLAGS: 00000246
RAX: 1ffff1100e8a8230 RBX: 0000000063760784 RCX: dffffc0000000000
RDX: ffff888028d65940 RSI: 0000000063760784 RDI: ffff888074541180
RBP: 000000002d680538 R08: ffffffff81f87c19 R09: fffffbfff2093858
R10: 0000000000000000 R11: dffffc0000000001 R12: 00000000664a30d5
R13: dffffc0000000000 R14: ffff888074541110 R15: 0000000007e27e60
 touch_atime+0xe4/0x680 fs/inode.c:1970
 file_accessed include/linux/fs.h:2595 [inline]
 filemap_read+0x2ef3/0x31d0 mm/filemap.c:2807
 __kernel_read+0x41e/0x8a0 fs/read_write.c:428
 integrity_kernel_read+0xac/0xf0 security/integrity/iint.c:228
 ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:485 [inline]
 ima_calc_file_shash security/integrity/ima/ima_crypto.c:516 [inline]
 ima_calc_file_hash+0xa57/0x1c00 security/integrity/ima/ima_crypto.c:573
 ima_collect_measurement+0x59a/0xc30 security/integrity/ima/ima_api.c:293
 process_measurement+0x135c/0x21b0 security/integrity/ima/ima_main.c:351
 ima_file_check+0xed/0x170 security/integrity/ima/ima_main.c:534
 do_open fs/namei.c:3630 [inline]
 path_openat+0x2687/0x2e60 fs/namei.c:3785
 do_filp_open+0x230/0x480 fs/namei.c:3812
 do_sys_openat2+0x13b/0x500 fs/open.c:1318
 do_sys_open fs/open.c:1334 [inline]
 __do_sys_openat fs/open.c:1350 [inline]
 __se_sys_openat fs/open.c:1345 [inline]
 __x64_sys_openat+0x243/0x290 fs/open.c:1345
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f266707cee9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f2667d530c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f26671abf80 RCX: 00007f266707cee9
RDX: 000000000002a442 RSI: 00000000200001c0 RDI: ffffffffffffff9c
RBP: 00007f26670c949e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f26671abf80 R15: 00007ffceb75ed68
 </TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..
----------------
Code disassembly (best guess):
   0:	0f 11 92 ff eb 75 49 	movups %xmm2,0x4975ebff(%rdx)
   7:	8d 7e 70             	lea    0x70(%rsi),%edi
   a:	48 89 f8             	mov    %rdi,%rax
   d:	48 c1 e8 03          	shr    $0x3,%rax
  11:	48 b9 00 00 00 00 00 	movabs $0xdffffc0000000000,%rcx
  18:	fc ff df
  1b:	80 3c 08 00          	cmpb   $0x0,(%rax,%rcx,1)
  1f:	74 05                	je     0x26
  21:	e8 6d 90 e9 ff       	call   0xffe99093
  26:	49 8b 6e 70          	mov    0x70(%r14),%rbp
* 2a:	49 83 c6 60          	add    $0x60,%r14 <-- trapping instruction
  2e:	4c 89 f0             	mov    %r14,%rax
  31:	48 c1 e8 03          	shr    $0x3,%rax
  35:	48 b9 00 00 00 00 00 	movabs $0xdffffc0000000000,%rcx
  3c:	fc ff df
  3f:	80                   	.byte 0x80

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/05/19 17:03 linux-6.1.y 4078fa637fcd c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan kernel panic: stack is corrupted in __schedule
* Struck through repros no longer work on HEAD.