syzbot


WARNING in __set_page_dirty

Status: upstream: reported C repro on 2023/02/26 05:45
Reported-by: syzbot+e2aa8be6fa4bdbacfcd5@syzkaller.appspotmail.com
First crash: 472d, last: 472d
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 30235 6m 462d 0/3 upstream: reported C repro on 2023/03/08 14:57
android-44 WARNING in __set_page_dirty (2) 2 1670d 1678d 0/2 auto-closed as invalid on 2020/03/14 23:01
upstream WARNING in __set_page_dirty nilfs C error 9 833d 1057d 22/28 fixed on 2023/02/24 13:50
android-44 WARNING in __set_page_dirty 1 1840d 1840d 0/2 auto-closed as invalid on 2019/10/25 08:43
android-49 WARNING in __set_page_dirty 5 1992d 1886d 0/3 auto-closed as invalid on 2019/06/27 13:07
android-49 WARNING in __set_page_dirty (2) 1 1763d 1763d 0/3 auto-closed as invalid on 2019/12/13 14:34
linux-4.19 WARNING in __set_page_dirty C 10 471d 610d 0/1 upstream: reported C repro on 2022/10/11 13:48

Sample crash report:
EXT4-fs (loop3): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 2 with error 28
EXT4-fs (loop5): dirty_blocks=352
EXT4-fs (loop3): This should not happen!! Data will be lost
EXT4-fs (loop5): Block reservation details
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8222 at fs/buffer.c:633 __set_page_dirty+0x1fa/0x2a0 fs/buffer.c:633
EXT4-fs (loop5): i_reserved_data_blocks=22
Kernel panic - not syncing: kernel: panic_on_warn set ...

CPU: 0 PID: 8222 Comm: syz-executor218 Not tainted 4.14.307-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/2023
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x1b2/0x281 lib/dump_stack.c:58
 panic+0x21d/0x451 kernel/panic.c:247
 check_panic_on_warn.cold+0x19/0x35 kernel/panic.c:171
 __warn+0xdf/0x1e0 kernel/panic.c:603
 report_bug+0x208/0x250 lib/bug.c:183
 fixup_bug arch/x86/kernel/traps.c:177 [inline]
 fixup_bug arch/x86/kernel/traps.c:172 [inline]
 do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
 invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:967
RIP: 0010:__set_page_dirty+0x1fa/0x2a0 fs/buffer.c:633
RSP: 0018:ffff8880aafefb60 EFLAGS: 00010097
RAX: ffff8880abb26180 RBX: ffff88808dffe5c0 RCX: 0000000000007a19
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffea0002241288
RBP: ffffea0002241280 R08: ffffffff8b9e2c48 R09: 00000000000c023c
R10: ffff8880abb26aa8 R11: ffff8880abb26180 R12: 0000000000000282
R13: ffffea0002241280 R14: ffff88808dffe5d8 R15: ffffea00022412a0
 __set_page_dirty_buffers+0x15c/0x240 fs/buffer.c:693
 set_page_dirty+0x148/0x2a0 mm/page-writeback.c:2586
 block_page_mkwrite+0x1fa/0x2b0 fs/buffer.c:2557
 ext4_page_mkwrite+0x7c0/0xf70 fs/ext4/inode.c:6235
 do_page_mkwrite+0xd4/0x2e0 mm/memory.c:2492
 do_shared_fault mm/memory.c:3824 [inline]
 do_fault mm/memory.c:3889 [inline]
 handle_pte_fault mm/memory.c:4115 [inline]
 __handle_mm_fault+0x23e8/0x4620 mm/memory.c:4239
 handle_mm_fault+0x455/0x9c0 mm/memory.c:4276
 __do_page_fault+0x549/0xad0 arch/x86/mm/fault.c:1442
 page_fault+0x45/0x50 arch/x86/entry/entry_64.S:1126
RIP: 69662f2e:0xf6f2cbf92df09e20
RSP: 1acdf810:00007fca1acac858 EFLAGS: 7fca1acac0e0
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/02/26 11:49 linux-4.14.y 7878a41b6cc1 ee50e71c .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-linux-4-14 WARNING in __set_page_dirty
2023/02/26 05:44 linux-4.14.y 7878a41b6cc1 ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 WARNING in __set_page_dirty
* Struck through repros no longer work on HEAD.