corrupted report

Status: upstream: reported on 2023/03/07 17:14
Reported-by: syzbot+ea9a2d620e90898a0a2a@syzkaller.appspotmail.com
First crash: 1273d, last: 49m
Similar bugs (23)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-5-10 corrupted report (2) -1 6 1093d 1171d 0/2 auto-obsoleted due to no activity on 2023/12/02 13:09
android-54 corrupted report (2) -1 105976 462d 583d 0/2 auto-obsoleted due to no activity on 2025/07/15 11:08
linux-4.19 corrupted report gfs2 sysv ext4 hfsplus -1 6619 1274d 2699d 0/1 upstream: reported on 2019/04/11 04:14
android-414 corrupted report -1 5888 2465d 2700d 0/1 auto-closed as invalid on 2020/02/29 14:20
android-5-15 corrupted report -1 4 1142d 1224d 0/2 auto-obsoleted due to no activity on 2023/10/14 13:19
android-6-12 corrupted report -1 191 290d 435d 0/1 auto-obsoleted due to no activity on 2026/01/03 01:56
linux-6.6 corrupted report -1 12374 11m 440d 0/2 upstream: reported on 2025/06/16 23:08
upstream corrupted report -1 29 3202d 3204d 0/29 closed as invalid on 2017/11/24 12:19
android-54 corrupted report -1 860856 763d 2394d 0/2 auto-obsoleted due to no activity on 2024/10/07 14:17
linux-4.4 corrupted report -1 12 2545d 2673d 0/1 auto-closed as invalid on 2020/01/10 12:28
android-6-12 corrupted report (2) -1 1550 3h38m 222d 0/1 premoderation: reported on 2026/01/21 07:36
linux-4.14 corrupted report cramfs -1 6026 1274d 2697d 0/1 upstream: reported on 2019/04/12 21:21
android-6-1 corrupted report -1 640 7d21h 1132d 0/2 premoderation: reported on 2023/07/25 23:06
android-5-15 corrupted report (3) -1 71 655d 880d 0/2 auto-obsoleted due to no activity on 2025/01/03 14:55
android-5-10 corrupted report -1 289 1572d 1721d 0/2 auto-closed as invalid on 2022/07/11 05:59
android-49 corrupted report -1 567 3202d 3204d 0/3 closed as invalid on 2017/11/24 12:19
android-5-15 corrupted report (4) -1 418 10m 597d 0/2 premoderation: reported on 2025/01/11 16:11
android-5-15 corrupted report (2) -1 1 1003d 1003d 0/2 auto-obsoleted due to no activity on 2024/03/01 04:17
upstream corrupted report (2) prio:low net -1 1158338 24m 3064d 0/29 moderation: reported on 2018/04/11 09:52
linux-5.15 corrupted report -1 10794 5h16m 1267d 0/3 upstream: reported on 2023/03/12 22:30
android-49 corrupted report (2) -1 19181 2462d 2696d 0/3 auto-closed as invalid on 2020/03/03 12:39
android-5-10 corrupted report (3) -1 140 4d23h 875d 0/2 premoderation: reported on 2024/04/08 19:56
android-44 corrupted report -1 7075 2462d 2696d 0/2 auto-closed as invalid on 2020/03/02 23:26

Sample crash report:
loop5: detected capacity change from 0 to 32768
ocfs2: Mounting device (7,5) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.5.2813/12222 is trying to acquire lock:
ffff8880559e22e0 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_try_remove_refcount_tree+0xb3/0x360 fs/ocfs2/refcounttree.c:932

but task is already holding lock:
ffff8880559e2378 (&oi->ip_xattr_sem){++++}-{3:3}, at: ocfs2_try_remove_refcount_tree+0xa1/0x360 fs/ocfs2/refcounttree.c:931

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&oi->ip_xattr_sem){++++}-{3:3}:
       down_read+0x42/0x2d0 kernel/locking/rwsem.c:1520
       ocfs2_init_acl+0x307/0x770 fs/ocfs2/acl.c:365
       ocfs2_mknod+0x18e0/0x2580 fs/ocfs2/namei.c:410
       ocfs2_mkdir+0x1b6/0x4b0 fs/ocfs2/namei.c:657
       vfs_mkdir+0x386/0x570 fs/namei.c:4157
       do_mkdirat+0x1d8/0x440 fs/namei.c:4182
       __do_sys_mkdir fs/namei.c:4202 [inline]
       __se_sys_mkdir fs/namei.c:4200 [inline]
       __x64_sys_mkdir+0x6a/0x80 fs/namei.c:4200
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #2 (&journal->j_trans_barrier){.+.+}-{3:3}:
       down_read+0x42/0x2d0 kernel/locking/rwsem.c:1520
       ocfs2_start_trans+0x3a4/0x6f0 fs/ocfs2/journal.c:374
       ocfs2_local_alloc_slide_window fs/ocfs2/localalloc.c:1258 [inline]
       ocfs2_reserve_local_alloc_bits+0xaad/0x2770 fs/ocfs2/localalloc.c:668
       ocfs2_reserve_clusters_with_limit+0x1b6/0xc10 fs/ocfs2/suballoc.c:1184
       ocfs2_expand_inline_dir fs/ocfs2/dir.c:2855 [inline]
       ocfs2_extend_dir+0x77b/0x4c40 fs/ocfs2/dir.c:3200
       ocfs2_prepare_dir_for_insert+0x3217/0x5600 fs/ocfs2/dir.c:4321
       ocfs2_mknod+0xb46/0x2580 fs/ocfs2/namei.c:294
       ocfs2_mkdir+0x1b6/0x4b0 fs/ocfs2/namei.c:657
       vfs_mkdir+0x386/0x570 fs/namei.c:4157
       do_mkdirat+0x1d8/0x440 fs/namei.c:4182
       __do_sys_mkdirat fs/namei.c:4197 [inline]
       __se_sys_mkdirat fs/namei.c:4195 [inline]
       __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4195
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #1 (sb_internal#2){.+.+}-{0:0}:
       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
       __sb_start_write include/linux/fs.h:1897 [inline]
       sb_start_intwrite include/linux/fs.h:2019 [inline]
       ocfs2_start_trans+0x2a5/0x6f0 fs/ocfs2/journal.c:372
       ocfs2_extend_dir+0x11bd/0x4c40 fs/ocfs2/dir.c:3287
       ocfs2_prepare_dir_for_insert+0x3217/0x5600 fs/ocfs2/dir.c:4321
       ocfs2_mknod+0xb46/0x2580 fs/ocfs2/namei.c:294
       vfs_mknod+0x430/0x4c0 fs/namei.c:4036
       do_mknodat+0x356/0x4d0 fs/namei.c:-1
       __do_sys_mknod fs/namei.c:4119 [inline]
       __se_sys_mknod fs/namei.c:4117 [inline]
       __x64_sys_mknod+0x8a/0xa0 fs/namei.c:4117
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3095 [inline]
       check_prevs_add kernel/locking/lockdep.c:3214 [inline]
       validate_chain kernel/locking/lockdep.c:3830 [inline]
       __lock_acquire+0x2d18/0x7c40 kernel/locking/lockdep.c:5063
       lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676
       down_write+0x36/0x60 kernel/locking/rwsem.c:1573
       ocfs2_try_remove_refcount_tree+0xb3/0x360 fs/ocfs2/refcounttree.c:932
       ocfs2_truncate_file+0xef5/0x1660 fs/ocfs2/file.c:517
       ocfs2_setattr+0x16f8/0x1d90 fs/ocfs2/file.c:1212
       notify_change+0xca0/0xf90 fs/attr.c:499
       do_truncate+0x1ac/0x240 fs/open.c:65
       handle_truncate fs/namei.c:3336 [inline]
       do_open fs/namei.c:3681 [inline]
       path_openat+0x2897/0x2f10 fs/namei.c:3834
       do_filp_open+0x1ee/0x420 fs/namei.c:3861
       do_sys_openat2+0x14b/0x4f0 fs/open.c:1320
       do_sys_open fs/open.c:1336 [inline]
       __do_sys_creat fs/open.c:1414 [inline]
       __se_sys_creat fs/open.c:1408 [inline]
       __x64_sys_creat+0x8c/0xb0 fs/open.c:1408
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

other info that might help us debug this:

Chain exists of:
  &ocfs2_file_ip_alloc_sem_key --> &journal->j_trans_barrier --> &oi->ip_xattr_sem

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&oi->ip_xattr_sem);
                               lock(&journal->j_trans_barrier);
                               lock(&oi->ip_xattr_sem);
  lock(&ocfs2_file_ip_alloc_sem_key);

 *** DEADLOCK ***

3 locks held by syz.5.2813/12222:
 #0: ffff8880795c6460 (sb_writers#17){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:402
 #1: ffff8880559e2648 (&sb->s_type->i_mutex_key#24){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:764 [inline]
 #1: ffff8880559e2648 (&sb->s_type->i_mutex_key#24){+.+.}-{3:3}, at: do_truncate+0x198/0x240 fs/open.c:63
 #2: ffff8880559e2378 (&oi->ip_xattr_sem){++++}-{3:3}, at: ocfs2_try_remove_refcount_tree+0xa1/0x360 fs/ocfs2/refcounttree.c:931

stack backtrace:
CPU: 0 PID: 12222 Comm: syz.5.2813 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2170
 check_prev_add kernel/locking/lockdep.c:3095 [inline]
 check_prevs_add kernel/locking/lockdep.c:3214 [inline]
 validate_chain kernel/locking/lockdep.c:3830 [inline]
 __lock_acquire+0x2d18/0x7c40 kernel/locking/lockdep.c:5063
 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676
 down_write+0x36/0x60 kernel/locking/rwsem.c:1573
 ocfs2_try_remove_refcount_tree+0xb3/0x360 fs/ocfs2/refcounttree.c:932
 ocfs2_truncate_file+0xef5/0x1660 fs/ocfs2/file.c:517
 ocfs2_setattr+0x16f8/0x1d90 fs/ocfs2/file.c:1212
 notify_change+0xca0/0xf90 fs/attr.c:499
 do_truncate+0x1ac/0x240 fs/open.c:65
 handle_truncate fs/namei.c:3336 [inline]
 do_open fs/namei.c:3681 [inline]
 path_openat+0x2897/0x2f10 fs/namei.c:3834
 do_filp_open+0x1ee/0x420 fs/namei.c:3861
 do_sys_openat2+0x14b/0x4f0 fs/open.c:1320
 do_sys_open fs/open.c:1336 [inline]
 __do_sys_creat fs/open.c:1414 [inline]
 __se_sys_creat fs/open.c:1408 [inline]
 __x64_sys_creat+0x8c/0xb0 fs/open.c:1408
 do_syscall_x64 arch/x86/entry/common.c:46 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f0d85d9e159
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f0d86c5f028 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007f0d86025fa0 RCX: 00007f0d85d9e159
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000200000000ac0
RBP: 00007f0d85e35024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f0d86026038 R14: 00007f0d86025fa0 R15: 00007ffd0c4a6e68
 </TASK>

Crashes (191327):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/31 18:15 linux-6.1.y d64a499eea6b 316d9396 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan corrupted report
2026/08/31 17:02 linux-6.1.y d64a499eea6b 316d9396 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan corrupted report
2026/08/31 14:02 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/31 12:54 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan corrupted report
2026/08/31 10:31 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/31 09:02 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/31 06:54 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/31 04:36 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/31 01:11 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan corrupted report
2026/08/31 00:20 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/30 16:38 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/30 13:48 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/30 09:11 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/30 07:32 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/30 06:05 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/30 01:37 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/29 23:27 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/29 22:21 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/29 20:35 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/29 19:13 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/29 19:03 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/29 11:23 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/29 06:20 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan corrupted report
2026/08/29 02:38 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan corrupted report
2026/08/28 23:09 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan corrupted report
2026/08/28 18:08 linux-6.1.y d64a499eea6b e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/28 14:58 linux-6.1.y d64a499eea6b e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/28 13:37 linux-6.1.y d64a499eea6b e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/28 05:50 linux-6.1.y 79a9660d699e 69a01293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/28 03:07 linux-6.1.y 79a9660d699e 69a01293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/28 00:27 linux-6.1.y 79a9660d699e 69a01293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/27 21:34 linux-6.1.y 79a9660d699e 69a01293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/27 19:09 linux-6.1.y 79a9660d699e 69a01293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/27 10:08 linux-6.1.y 05208478041c a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/27 08:04 linux-6.1.y 05208478041c a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/27 06:43 linux-6.1.y 05208478041c a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
2026/08/31 19:17 linux-6.1.y d64a499eea6b 316d9396 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 corrupted report
2026/08/31 05:47 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 corrupted report
2026/08/30 04:01 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 corrupted report
2026/08/29 09:37 linux-6.1.y d64a499eea6b 2f52988a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 corrupted report
2026/08/28 10:26 linux-6.1.y d64a499eea6b e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 corrupted report
2026/08/28 10:25 linux-6.1.y d64a499eea6b e2fa417d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 corrupted report
2026/08/27 17:54 linux-6.1.y 79a9660d699e 69a01293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 corrupted report
2026/08/27 13:09 linux-6.1.y 05208478041c 69a01293 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 corrupted report
2026/08/27 07:53 linux-6.1.y 05208478041c a2b77b9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 corrupted report
2023/03/07 17:14 linux-6.1.y 42616e0f09fb d7ea8bc4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf corrupted report
* Struck through repros no longer work on HEAD.