syzbot


WARNING in __set_page_dirty

Status: upstream: reported C repro on 2022/10/11 13:48
Reported-by: syzbot+d9c62fc2a488273004e9@syzkaller.appspotmail.com
First crash: 784d, last: 646d
Similar bugs (7)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 WARNING in __set_page_dirty origin:upstream C 157951 40m 636d 0/3 upstream: reported C repro on 2023/03/08 14:57
linux-4.14 WARNING in __set_page_dirty C 2 646d 647d 0/1 upstream: reported C repro on 2023/02/26 05:45
android-44 WARNING in __set_page_dirty (2) 2 1845d 1853d 0/2 auto-closed as invalid on 2020/03/14 23:01
upstream WARNING in __set_page_dirty nilfs C error 9 1008d 1232d 22/28 fixed on 2023/02/24 13:50
android-44 WARNING in __set_page_dirty 1 2015d 2015d 0/2 auto-closed as invalid on 2019/10/25 08:43
android-49 WARNING in __set_page_dirty 5 2166d 2060d 0/3 auto-closed as invalid on 2019/06/27 13:07
android-49 WARNING in __set_page_dirty (2) 1 1937d 1937d 0/3 auto-closed as invalid on 2019/12/13 14:34

Sample crash report:
EXT4-fs (loop0): dirty_blocks=1952
EXT4-fs (loop0): Block reservation details
EXT4-fs (loop0): i_reserved_data_blocks=122
EXT4-fs (loop0): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 2 with error 28
EXT4-fs (loop0): This should not happen!! Data will be lost
WARNING: CPU: 1 PID: 18696 at fs/buffer.c:581 __set_page_dirty+0x2e3/0x3e0 fs/buffer.c:581
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 18696 Comm: syz-executor343 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/2023
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
 panic+0x26a/0x50e kernel/panic.c:186
 __warn.cold+0x20/0x5a kernel/panic.c:541
 report_bug+0x262/0x2b0 lib/bug.c:183
 fixup_bug arch/x86/kernel/traps.c:178 [inline]
 fixup_bug arch/x86/kernel/traps.c:173 [inline]
 do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
 invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:__set_page_dirty+0x2e3/0x3e0 fs/buffer.c:581
Code: 01 89 de e8 2f 40 b2 ff 84 db 0f 84 de fe ff ff e8 f2 3e b2 ff 48 89 ef e8 2a dd e1 ff 48 89 c5 e9 f1 fe ff ff e8 dd 3e b2 ff <0f> 0b e9 85 fd ff ff e8 d1 3e b2 ff 4d 8d 67 ff e9 c2 fd ff ff e8
RSP: 0018:ffff8880a202fa28 EFLAGS: 00010093
RAX: ffff8880a91da1c0 RBX: 0000000000000000 RCX: ffffffff81b0462f
RDX: 0000000000000000 RSI: ffffffff81b04693 RDI: 0000000000000001
RBP: ffffea00022237c0 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: ffff8880893b3978
R13: 0000000000000286 R14: ffff8880893b3980 R15: ffffea00022237c8
 __set_page_dirty_buffers+0x27b/0x4c0 fs/buffer.c:642
 set_page_dirty+0x25f/0x640 mm/page-writeback.c:2569
 block_page_mkwrite+0x246/0x300 fs/buffer.c:2500
 ext4_page_mkwrite+0xca7/0x1320 fs/ext4/inode.c:6304
 do_page_mkwrite+0xd4/0x410 mm/memory.c:2486
 wp_page_shared mm/memory.c:2794 [inline]
 do_wp_page+0x980/0x2210 mm/memory.c:2894
 handle_pte_fault mm/memory.c:4191 [inline]
 __handle_mm_fault+0x258b/0x41c0 mm/memory.c:4299
 handle_mm_fault+0x436/0xb10 mm/memory.c:4336
 __do_page_fault+0x68e/0xd60 arch/x86/mm/fault.c:1412
 page_fault+0x1e/0x30 arch/x86/entry/entry_64.S:1205
RIP: 0033:0x7f599ba72d70
Code: 09 00 0f 29 04 25 50 00 00 20 e9 02 fd ff ff 0f 1f 00 48 b8 2e 2f 66 69 6c 65 30 00 48 89 04 25 c0 07 00 20 e9 11 fc ff ff 90 <c7> 04 25 80 07 00 20 65 78 74 34 c6 04 25 84 07 00 20 00 e9 c7 fb
RSP: 002b:00007f599b263210 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 00007f599bb4b548 RCX: 00007f599bac6249
RDX: 20dd6f6f4162c484 RSI: 0000000000000000 RDI: 00007f599b2635e8
RBP: 00007f599bb4b540 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f599bb4b54c
R13: 00007fff385589ef R14: 00007f599b263300 R15: 0000000000022000
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (10):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/02/27 01:10 linux-4.19.y 3f8a27f9e27b ee50e71c .config console log report syz C [disk image] [vmlinux] [mounted in repro #1] [mounted in repro #2] ci2-linux-4-19 WARNING in __set_page_dirty
2023/02/26 13:59 linux-4.19.y 3f8a27f9e27b ee50e71c .config console log report info [disk image] [vmlinux] ci2-linux-4-19 WARNING in __set_page_dirty
2023/02/08 05:51 linux-4.19.y 3f8a27f9e27b 15c3d445 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 WARNING in __set_page_dirty
2023/01/03 10:16 linux-4.19.y 3f8a27f9e27b ab32d508 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 WARNING in __set_page_dirty
2023/01/01 19:18 linux-4.19.y 3f8a27f9e27b ab32d508 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 WARNING in __set_page_dirty
2022/12/22 06:50 linux-4.19.y 3f8a27f9e27b 4067838e .config console log report info [disk image] [vmlinux] ci2-linux-4-19 WARNING in __set_page_dirty
2022/12/05 20:32 linux-4.19.y 3f8a27f9e27b 045cbb84 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 WARNING in __set_page_dirty
2022/11/20 11:14 linux-4.19.y 3f8a27f9e27b 5bb70014 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 WARNING in __set_page_dirty
2022/10/17 01:03 linux-4.19.y 3f8a27f9e27b 67cb024c .config console log report info [disk image] [vmlinux] ci2-linux-4-19 WARNING in __set_page_dirty
2022/10/11 13:47 linux-4.19.y 3f8a27f9e27b 5bcf0c31 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 WARNING in __set_page_dirty
* Struck through repros no longer work on HEAD.