Hello,
syzbot found the following issue on:
HEAD commit: 015e94d0 Linux 4.19.146
git tree: linux-4.19.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=12cc4cbb900000
kernel config:
https://syzkaller.appspot.com/x/.config?x=243dd74ad58a8a57
dashboard link:
https://syzkaller.appspot.com/bug?extid=bb6a32b547830c3c740d
compiler: gcc (GCC) 10.1.0-syz 20200507
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+bb6a32...@syzkaller.appspotmail.com
WARNING: CPU: 1 PID: 6489 at include/linux/backing-dev.h:339 inode_to_wb include/linux/backing-dev.h:339 [inline]
WARNING: CPU: 1 PID: 6489 at include/linux/backing-dev.h:339 account_page_dirtied+0x8e9/0xbe0 mm/page-writeback.c:2420
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 6489 Comm: syz-executor.3 Not tainted 4.19.146-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x22c/0x33e lib/dump_stack.c:118
panic+0x2ac/0x565 kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1e1/0x330 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:inode_to_wb include/linux/backing-dev.h:339 [inline]
RIP: 0010:account_page_dirtied+0x8e9/0xbe0 mm/page-writeback.c:2420
Code: 88 01 00 00 be ff ff ff ff 48 8d 78 70 e8 0f 30 c6 ff 31 ff 89 c3 89 c6 e8 34 a5 e0 ff 85 db 0f 85 1c f9 ff ff e8 b7 a3 e0 ff <0f> 0b e9 10 f9 ff ff e8 ab a3 e0 ff 4c 89 e6 4c 89 ef e8 a0 d2 2f
RSP: 0018:ffff8880823ef7e8 EFLAGS: 00010093
RAX: ffff8880823e4640 RBX: 0000000000000000 RCX: ffffffff81911f1c
RDX: 0000000000000000 RSI: ffffffff81911f29 RDI: 0000000000000005
RBP: ffff8880a670ba60 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000004 R12: ffffea00023e8280
R13: ffff8880a670b8d8 R14: ffff888049691420 R15: ffffea00023e8288
__set_page_dirty+0x7f/0x3f0 fs/buffer.c:582
mark_buffer_dirty+0x442/0x5f0 fs/buffer.c:1111
gfs2_unpin+0xd6/0xeb0 fs/gfs2/lops.c:108
buf_lo_after_commit+0x140/0x210 fs/gfs2/lops.c:512
lops_after_commit fs/gfs2/lops.h:67 [inline]
gfs2_log_flush+0xa98/0x2030 fs/gfs2/log.c:833
do_sync+0x5d0/0xdf0 fs/gfs2/quota.c:961
gfs2_quota_sync+0x2dd/0x640 fs/gfs2/quota.c:1303
gfs2_sync_fs+0x40/0xb0 fs/gfs2/super.c:956
__sync_filesystem fs/sync.c:39 [inline]
sync_filesystem+0x105/0x250 fs/sync.c:64
generic_shutdown_super+0x70/0x370 fs/super.c:442
kill_block_super+0x97/0xf0 fs/super.c:1185
gfs2_kill_sb+0x12c/0x1a0 fs/gfs2/ops_fstype.c:1386
deactivate_locked_super+0x8c/0x100 fs/super.c:329
deactivate_super+0x174/0x1a0 fs/super.c:360
cleanup_mnt+0x1da/0x300 fs/namespace.c:1098
task_work_run+0x141/0x1c0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x269/0x2c0 arch/x86/entry/common.c:167
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x57c/0x670 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x460ba7
Code: 64 89 04 25 d0 02 00 00 58 5f ff d0 48 89 c7 e8 2f be ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 a6 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 dd 87 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007ffec0924d08 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000460ba7
RDX: 00000000004031b8 RSI: 0000000000000002 RDI: 00007ffec0924db0
RBP: 0000000000000012 R08: 0000000000000000 R09: 0000000000000009
R10: 0000000000000005 R11: 0000000000000246 R12: 00007ffec0925e40
R13: 0000000002f04a60 R14: 0000000000000000 R15: 00007ffec0925e40
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.