syzbot


kernel panic: stack is corrupted in lock_release (3)

Status: auto-obsoleted due to no activity on 2024/01/27 07:30
Subsystems: ntfs3
[Documentation on labels]
Reported-by: syzbot+4353c86db4e58720cd11@syzkaller.appspotmail.com
First crash: 521d, last: 129d
Cause bisection: failed (error log, bisect log)
  
Fix bisection: fixed by (bisect log) [merge ignored commit]:
commit 6bc40e44f1ddef16a787f3501b97f1fff909177c
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Fri Nov 17 14:18:48 2023 +0000

  Merge tag 'ovl-fixes-6.7-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/overlayfs/vfs

  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] kernel panic: stack is corrupted in lock_release (3) 1 (2) 2022/09/25 13:41
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream kernel panic: stack is corrupted in lock_release kernel 4 1877d 1879d 0/26 closed as dup on 2019/01/04 11:20
upstream kernel panic: stack is corrupted in lock_release (2) kernel syz error error 27 1589d 1637d 0/26 auto-obsoleted due to no activity on 2022/09/01 14:45
Last patch testing requests (1)
Created Duration User Patch Repo Result
2023/09/09 20:18 19m retest repro upstream OK log
Fix bisection attempts (10)
Created Duration User Patch Repo Result
2023/11/22 02:13 6h45m bisect fix upstream job log (1)
2023/10/19 05:08 2h21m bisect fix upstream job log (0) log
2023/09/15 10:06 2h19m bisect fix upstream job log (0) log
2023/07/01 16:35 1h32m bisect fix upstream job log (0) log
2023/06/01 06:56 59m bisect fix upstream job log (0) log
2023/05/02 05:00 1h08m bisect fix upstream job log (0) log
2023/04/01 21:10 55m bisect fix upstream job log (0) log
2023/03/02 20:08 1h01m bisect fix upstream job log (0) log
2023/01/31 03:37 1h00m bisect fix upstream job log (0) log
2022/11/07 12:39 55m bisect fix upstream job log (0) log

Sample crash report:
loop0: detected capacity change from 0 to 264192
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: lock_release+0x7f4/0x820
CPU: 0 PID: 9489 Comm: syz-executor322 Not tainted 6.0.0-rc6-syzkaller-00291-g3db61221f4e8 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106
 panic+0x2d6/0x715 kernel/panic.c:274
 __stack_chk_fail+0x12/0x20 kernel/panic.c:706
 lock_release+0x7f4/0x820
 __raw_spin_unlock include/linux/spinlock_api_smp.h:141 [inline]
 _raw_spin_unlock+0x12/0x40 kernel/locking/spinlock.c:186
 spin_unlock include/linux/spinlock.h:389 [inline]
 inode_wait_for_writeback+0x242/0x2c0 fs/fs-writeback.c:1474
 evict+0x277/0x620 fs/inode.c:662
 ntfs_fill_super+0x3af3/0x42a0 fs/ntfs3/super.c:1190
 get_tree_bdev+0x400/0x620 fs/super.c:1323
 vfs_get_tree+0x88/0x270 fs/super.c:1530
 do_new_mount+0x289/0xad0 fs/namespace.c:3040
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount+0x2d3/0x3c0 fs/namespace.c:3568
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fe603d0835a
Code: 48 c7 c2 c0 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 08 01 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd6ef632a8 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffd6ef63300 RCX: 00007fe603d0835a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007ffd6ef632c0
RBP: 00007ffd6ef632c0 R08: 00007ffd6ef63300 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000286 R12: 0000000020000bc0
R13: 0000000000000003 R14: 0000000000000004 R15: 0000000000000068
 </TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (8):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/09/25 00:57 upstream 3db61221f4e8 0042f2b4 .config console log report syz C ci2-upstream-fs kernel panic: stack is corrupted in lock_release
2022/12/16 11:00 upstream 84e57d292203 fcac021f .config console log report info ci-qemu-upstream kernel panic: stack is corrupted in lock_release
2022/10/08 03:35 upstream 4c86114194e6 79a59635 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in lock_release
2022/10/07 13:13 upstream 4c86114194e6 79a59635 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in lock_release
2022/10/07 03:11 upstream 833477fce7a1 80b58a42 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in lock_release
2022/09/30 05:39 upstream c3e0e1e23c70 45fd7169 .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in lock_release
2022/09/26 21:54 upstream f76349cf4145 d59ba983 .config console log report info ci2-upstream-fs kernel panic: stack is corrupted in lock_release
2022/09/21 10:36 upstream 60891ec99e14 380f82fb .config console log report info [disk image] [vmlinux] ci2-upstream-fs kernel panic: stack is corrupted in lock_release
* Struck through repros no longer work on HEAD.