syzbot

 sign-in | mailing list | source | docs
🐞 Open [984] ≡ Subsystems 🐞 Fixed [5216] 🐞 Invalid [12476] ⬇ Missing Backports [82] 📈 Kernel Health 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes 💬 Send us feedback

WARNING in ext4_da_update_reserve_space (2)

Status: auto-obsoleted due to no activity on 2023/09/27 10:25
Subsystems: ext4
[Documentation on labels]
Reported-by: syzbot+a1232eabd7a3d43d4fb5@syzkaller.appspotmail.com
First crash: 394d, last: 316d
Cause bisection: failed (error log, bisect log)
  
Fix bisection: failed (error log, bisect log)
  
▶ ▼ Discussions (2)
Title Replies (including bot) Last reply
[syzbot] Monthly ext4 report (May 2023) 5 (6) 2023/06/03 06:20
[syzbot] [ext4?] WARNING in ext4_da_update_reserve_space (2) 0 (1) 2023/03/26 10:44
▶ ▼ Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream WARNING in ext4_da_update_reserve_space ext4 C done error 2 1482d 1478d 0/26 auto-obsoleted due to no activity on 2022/09/07 06:28
linux-5.15 WARNING in ext4_da_update_reserve_space 1 369d 369d 0/3 auto-obsoleted due to no activity on 2023/08/14 09:33
▶ ▼ Last patch testing requests (4)
Created Duration User Patch Repo Result
2023/09/27 10:01 23m retest repro upstream OK log
2023/08/17 04:24 31m retest repro upstream OK log
2023/08/17 04:18 27m retest repro upstream OK log
2023/06/02 03:23 34m tytso@mit.edu patch git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git ext4_for_linus_stable OK log
▶ ▼ Fix bisection attempts (2)
Created Duration User Patch Repo Result
2023/07/18 20:19 12h28m bisect fix upstream error job log (0)
2023/05/26 22:30 1h02m bisect fix upstream job log (0) log

Sample crash report:
EXT4-fs warning (device loop1): ext4_da_update_reserve_space:372: ext4_da_update_reserve_space: ino 18, used 1 with only 0 reserved data blocks
------------[ cut here ]------------
WARNING: CPU: 1 PID: 41 at fs/ext4/inode.c:373 ext4_da_update_reserve_space+0x419/0x730 fs/ext4/inode.c:369
Modules linked in:
CPU: 1 PID: 41 Comm: kworker/u4:2 Not tainted 6.3.0-rc3-syzkaller-00026-gfff5a5e7f528 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: writeback wb_workfn (flush-7:1)
RIP: 0010:ext4_da_update_reserve_space+0x419/0x730 fs/ext4/inode.c:373
Code: 4c 89 ff 48 c7 c6 69 9e 82 8c ba 74 01 00 00 48 c7 c1 c0 3c fc 8a 49 c7 c0 69 9e 82 8c 41 55 41 54 e8 9b bb 0e 00 48 83 c4 10 <0f> 0b 48 bd 00 00 00 00 00 fc ff df 0f b6 04 2b 84 c0 0f 85 8f 01
RSP: 0018:ffffc90000b26cd0 EFLAGS: 00010282
RAX: cf4d35dbf73d9100 RBX: 1ffff1100e9b024d RCX: cf4d35dbf73d9100
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffff888074d80cf8 R08: ffffffff816dfe9c R09: fffffbfff205be51
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000001
R13: 0000000000000000 R14: ffff888074d80cb8 R15: ffff88807db7e000
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffc7e69ab88 CR3: 00000000764a4000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 ext4_map_blocks+0xb64/0x1cf0 fs/ext4/inode.c:672
 mpage_map_one_extent fs/ext4/inode.c:2421 [inline]
 mpage_map_and_submit_extent fs/ext4/inode.c:2474 [inline]
 ext4_do_writepages+0x189f/0x3d20 fs/ext4/inode.c:2876
 ext4_writepages+0x1e5/0x290 fs/ext4/inode.c:2964
 do_writepages+0x3a6/0x670 mm/page-writeback.c:2551
 __writeback_single_inode+0x155/0xfb0 fs/fs-writeback.c:1600
 writeback_sb_inodes+0x8ef/0x11d0 fs/fs-writeback.c:1891
 wb_writeback+0x458/0xc70 fs/fs-writeback.c:2065
 wb_do_writeback fs/fs-writeback.c:2208 [inline]
 wb_workfn+0x400/0xff0 fs/fs-writeback.c:2248
 process_one_work+0x8a0/0x10e0 kernel/workqueue.c:2390
 worker_thread+0xa63/0x1210 kernel/workqueue.c:2537
 kthread+0x270/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>

Crashes (9):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/03/23 03:59 upstream fff5a5e7f528 f94b4a29 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs WARNING in ext4_da_update_reserve_space
2023/06/08 04:13 upstream a27648c74210 7086cdb9 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root WARNING in ext4_da_update_reserve_space
2023/03/22 12:16 upstream a1effab7a3a3 8b4eb097 .config console log report syz [mounted in repro] ci2-upstream-fs WARNING in ext4_da_update_reserve_space
2023/04/22 14:15 upstream 8e41e0a57566 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_da_update_reserve_space
2023/04/17 04:30 upstream 3e7bb4f24617 ec410564 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root WARNING in ext4_da_update_reserve_space
2023/04/17 01:55 upstream 6a8f57ae2eb0 ec410564 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_da_update_reserve_space
2023/03/27 01:31 upstream 18940c888c85 fbf0499a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_da_update_reserve_space
2023/03/22 23:20 upstream fff5a5e7f528 f94b4a29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in ext4_da_update_reserve_space
2023/03/22 10:33 upstream a1effab7a3a3 8b4eb097 .config console log report info ci2-upstream-fs WARNING in ext4_da_update_reserve_space
* Struck through repros no longer work on HEAD.