WARNING in mark_buffer_dirty

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: b0cdffaa Linux 4.14.163
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10b42515e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=19269c071a1fe30
dashboard link: https://syzkaller.appspot.com/bug?extid=99bb7252befadd8e699f
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

Unfortunately, I don't have any reproducer for this crash yet.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+99bb72...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 1 PID: 7550 at fs/buffer.c:1149 mark_buffer_dirty+0x369/0x4a0
fs/buffer.c:1149
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 7550 Comm: syz-executor.1 Not tainted 4.14.163-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x142/0x197 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x2f/0x2f kernel/panic.c:547
report_bug+0x216/0x254 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x1bb/0x310 arch/x86/kernel/traps.c:295
do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:314
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:963
RIP: 0010:mark_buffer_dirty+0x369/0x4a0 fs/buffer.c:1149
RSP: 0018:ffff88804d5ef878 EFLAGS: 00010216
RAX: 0000000000040000 RBX: ffff88808fd95c78 RCX: ffffc90007035000
RDX: 00000000000035de RSI: ffffffff819b7029 RDI: ffff88808fd95c78
RBP: ffff88804d5ef898 R08: ffffed1009f96500 R09: 0000000000000000
R10: ffffed1009f964ff R11: ffff88804fcb27ff R12: ffff888094385d20
R13: ffff888077644780 R14: ffffed100eec8915 R15: ffff88808fd95c78
bfs_move_block fs/bfs/file.c:43 [inline]
bfs_move_blocks fs/bfs/file.c:56 [inline]
bfs_get_block+0x356/0xb50 fs/bfs/file.c:125
__block_write_begin_int+0x396/0x1100 fs/buffer.c:2027
__block_write_begin fs/buffer.c:2077 [inline]
block_write_begin+0x5f/0x280 fs/buffer.c:2136
bfs_write_begin+0x3a/0xc0 fs/bfs/file.c:177
generic_perform_write+0x1f8/0x480 mm/filemap.c:3047
__generic_file_write_iter+0x239/0x5b0 mm/filemap.c:3172
generic_file_write_iter+0x303/0x660 mm/filemap.c:3200
call_write_iter include/linux/fs.h:1777 [inline]
new_sync_write fs/read_write.c:469 [inline]
__vfs_write+0x4a7/0x6b0 fs/read_write.c:482
vfs_write+0x198/0x500 fs/read_write.c:544
SYSC_write fs/read_write.c:590 [inline]
SyS_write+0xfd/0x230 fs/read_write.c:582
do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x45af49
RSP: 002b:00007fcf0c9bac78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045af49
RDX: 0000000008800000 RSI: 0000000020000240 RDI: 0000000000000006
RBP: 000000000075bfc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fcf0c9bb6d4
R13: 00000000004cccb2 R14: 00000000004e8000 R15: 00000000ffffffff
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.