syzbot


WARNING in mark_buffer_dirty

Status: upstream: reported C repro on 2025/07/12 17:25
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+1d3cc35f66cd8ede91bf@syzkaller.appspotmail.com
First crash: 5d05h, last: 2d03h
Bug presence (2)
Date Name Commit Repro Result
2025/07/15 linux-6.6.y (ToT) 9247f4e6573a C [report] WARNING in mark_buffer_dirty
2025/07/15 upstream (ToT) 155a3c003e55 C Didn't crash
Similar bugs (14)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 WARNING in mark_buffer_dirty bfs -1 C error 10 928d 1274d 0/1 upstream: reported C repro on 2022/01/20 22:23
upstream WARNING in mark_buffer_dirty (6) fs -1 C error 11669 72d 639d 28/29 fixed on 2025/05/06 15:33
upstream WARNING in mark_buffer_dirty (4) bfs nilfs -1 C inconclusive 1152 770d 1109d 22/29 fixed on 2023/06/08 14:41
android-44 WARNING in mark_buffer_dirty -1 2 2388d 2286d 0/2 auto-closed as invalid on 2019/07/01 11:44
upstream WARNING in mark_buffer_dirty fs -1 C 21 2417d 2800d 0/29 closed as invalid on 2019/07/24 04:22
linux-4.14 WARNING in mark_buffer_dirty (2) nilfs2 -1 C error 8 870d 1253d 0/1 upstream: reported C repro on 2022/02/10 08:17
upstream WARNING in mark_buffer_dirty (2) ext4 -1 665 1919d 2052d 0/29 auto-closed as invalid on 2020/07/14 01:44
upstream WARNING in mark_buffer_dirty (5) nilfs -1 C done 172 646d 766d 23/29 fixed on 2023/10/12 12:48
upstream WARNING in mark_buffer_dirty (7) bfs hfs -1 C 420 2h49m 68d 0/29 upstream: reported C repro on 2025/05/10 17:11
upstream WARNING in mark_buffer_dirty (3) ext4 -1 2 1601d 1614d 0/29 auto-closed as invalid on 2021/06/27 09:01
android-49 WARNING in mark_buffer_dirty -1 7 2233d 2286d 0/3 auto-closed as invalid on 2019/10/25 08:47
linux-4.14 WARNING in mark_buffer_dirty -1 1 2013d 2013d 0/1 auto-closed as invalid on 2020/05/11 07:45
linux-5.15 WARNING in mark_buffer_dirty origin:upstream -1 C error 290 9d11h 855d 0/3 upstream: reported C repro on 2023/03/15 22:22
linux-6.1 WARNING in mark_buffer_dirty origin:upstream -1 C error 352 4d14h 857d 0/3 upstream: reported C repro on 2023/03/13 14:09

Sample crash report:
------------[ cut here ]------------
WARNING: CPU: 1 PID: 6023 at fs/buffer.c:1188 mark_buffer_dirty+0x2bb/0x4d0 fs/buffer.c:1188
Modules linked in:
CPU: 1 PID: 6023 Comm: segctord Not tainted 6.6.97-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/19/2025
RIP: 0010:mark_buffer_dirty+0x2bb/0x4d0 fs/buffer.c:1188
Code: 00 00 00 5b 41 5c 41 5e 41 5f 5d e9 ef ac fc ff e8 ca 95 88 ff 48 89 df 5b 41 5c 41 5e 41 5f 5d e9 fa 57 e8 ff e8 b5 95 88 ff <0f> 0b e9 84 fd ff ff e8 a9 95 88 ff 0f 0b e9 b0 fd ff ff e8 9d 95
RSP: 0018:ffffc900036d76f0 EFLAGS: 00010293

RAX: ffffffff81fd00bb RBX: ffff888060268740 RCX: ffff888026a79e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
RBP: ffffc900036d7b01 R08: ffff888060268747 R09: 1ffff1100c04d0e8
R10: dffffc0000000000 R11: ffffed100c04d0e9 R12: 1ffff1100b6174f5
R13: ffff88805b0ba7b8 R14: ffff88805b0ba140 R15: 1ffff1100b6174f7
FS:  0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fefb0344000 CR3: 00000000262e1000 CR4: 00000000003506e0
Call Trace:
 <TASK>
 nilfs_segctor_collect_dirty_files fs/nilfs2/segment.c:2009 [inline]
 nilfs_segctor_do_construct+0x32c/0x6870 fs/nilfs2/segment.c:2071
 nilfs_segctor_construct+0x17b/0x690 fs/nilfs2/segment.c:2454
 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2562 [inline]
 nilfs_segctor_thread+0x4f6/0x1000 fs/nilfs2/segment.c:2646
 kthread+0x2fa/0x390 kernel/kthread.c:388
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
 </TASK>

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/12 18:26 linux-6.6.y 59a2de10b81a 3cda49cf .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-6-kasan WARNING in mark_buffer_dirty
2025/07/12 17:25 linux-6.6.y 59a2de10b81a 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan WARNING in mark_buffer_dirty
* Struck through repros no longer work on HEAD.