Hello,
syzbot found the following issue on:
HEAD commit: 7878a41b6cc1 Linux 4.14.307
git tree: linux-4.14.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=15ab9d50c80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=77c994a24403ce1c
dashboard link:
https://syzkaller.appspot.com/bug?extid=e2aa8be6fa4bdbacfcd5
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/1fdebf709d79/disk-7878a41b.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/88229e373f4d/vmlinux-7878a41b.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/bf3c4c287a8b/bzImage-7878a41b.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+e2aa8b...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 11850 at fs/buffer.c:633 __set_page_dirty+0x1fa/0x2a0 fs/buffer.c:633
Kernel panic - not syncing: kernel: panic_on_warn set ...
CPU: 0 PID: 11850 Comm: syz-executor.3 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:ffff88804709fac0 EFLAGS: 00010097
RAX: ffff8880aaaf4640 RBX: ffff8880537a6580 RCX: 00000000000072e7
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffea00013a2f88
RBP: ffffea00013a2f80 R08: ffffffff8b9df2b8 R09: 00000000000c023b
R10: ffff8880aaaf4f68 R11: ffff8880aaaf4640 R12: 0000000000000282
R13: ffffea00013a2f80 R14: ffff8880537a6598 R15: ffffea00013a2fa0
__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
wp_page_shared mm/memory.c:2796 [inline]
do_wp_page+0x7e2/0x1db0 mm/memory.c:2896
handle_pte_fault mm/memory.c:4131 [inline]
__handle_mm_fault+0x234f/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: ffb1e78:0x7f2a1055c530
RSP: 0000:00007ffd1d7ce5d8 EFLAGS: 7f2a1055c53c
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
This report is generated by a bot. It may contain errors.
See
https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.