WARNING in ext4_set_page_dirty

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 47350a9f ANDROID: x86_64_cuttlefish_defconfig: Enable lz4 ..
git tree: android-4.14
console output: https://syzkaller.appspot.com/x/log.txt?x=15cf44ea400000
kernel config: https://syzkaller.appspot.com/x/.config?x=10d236078f3378a3
dashboard link: https://syzkaller.appspot.com/bug?extid=bc4aa29af661cb610a97
compiler: gcc (GCC) 8.0.1 20180413 (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+bc4aa2...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 1 PID: 8477 at fs/ext4/inode.c:3893
ext4_set_page_dirty+0xfe/0x160 fs/ext4/inode.c:3893
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 8477 Comm: syz-executor0 Not tainted 4.14.67+ #1
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0xb9/0x11b lib/dump_stack.c:53
panic+0x1bf/0x3a4 kernel/panic.c:181
__warn.cold.7+0x148/0x185 kernel/panic.c:542
report_bug+0x1f7/0x26c lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
do_error_trap+0x1ba/0x2c0 arch/x86/kernel/traps.c:295
invalid_op+0x18/0x40 arch/x86/entry/entry_64.S:944
RIP: 0010:ext4_set_page_dirty+0xfe/0x160 fs/ext4/inode.c:3893
RSP: 0018:ffff8801ba6e75c0 EFLAGS: 00010216
RAX: 0000000000040000 RBX: ffffea00067a24c0 RCX: 0000000000013fb5
RDX: ffffffff8173924e RSI: ffffc90000690000 RDI: ffffea00067a24c0
RBP: ffffea00067a24c0 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffffea00067a24e0
R13: ffffea00067e0ee0 R14: ffffea00067e0ee0 R15: ffff8801cb091d40
set_page_dirty+0x15b/0x2c0 mm/page-writeback.c:2566
set_page_dirty_lock+0x61/0xa0 mm/page-writeback.c:2591
dio_bio_complete+0x3bd/0x510 fs/direct-io.c:538
dio_await_completion fs/direct-io.c:559 [inline]
do_blockdev_direct_IO fs/direct-io.c:1370 [inline]
__blockdev_direct_IO+0x758b/0xc4e0 fs/direct-io.c:1399
ext4_direct_IO_read fs/ext4/inode.c:3797 [inline]
ext4_direct_IO+0xbb8/0x27f0 fs/ext4/inode.c:3856
generic_file_read_iter+0x23e/0x1ab0 mm/filemap.c:2242
ext4_file_read_iter+0x114/0x160 fs/ext4/file.c:75
call_read_iter include/linux/fs.h:1776 [inline]
new_sync_read fs/read_write.c:401 [inline]
__vfs_read+0x414/0x5b0 fs/read_write.c:413
vfs_read+0x11e/0x330 fs/read_write.c:447
SYSC_pread64 fs/read_write.c:615 [inline]
SyS_pread64+0x136/0x160 fs/read_write.c:602
do_syscall_64+0x19b/0x4b0 arch/x86/entry/common.c:289
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x457099
RSP: 002b:00007f4ba9709c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000011
RAX: ffffffffffffffda RBX: 00007f4ba970a6d4 RCX: 0000000000457099
RDX: 00000000fffffd80 RSI: 0000000020002000 RDI: 0000000000000007
RBP: 0000000000930140 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000004d3bb8 R14: 00000000004c86c0 R15: 0000000000000001
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: 0x27e00000 from 0xffffffff81000000 (relocation range:
0xffffffff80000000-0xffffffffbfffffff)
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.