kernel BUG at mm/internal.h:LINE!

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b850307b Linux 4.14.184
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17fb526f100000
kernel config: https://syzkaller.appspot.com/x/.config?x=ddc0f08dd6b981c5
dashboard link: https://syzkaller.appspot.com/bug?extid=f0920e665cb8366248ef
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

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+f0920e...@syzkaller.appspotmail.com

next (null) prev (null) mm (null)
prot 0 anon_vma (null) vm_ops (null)
pgoff 0 file (null) private_data (null)
flags: 0x0()
------------[ cut here ]------------
kernel BUG at mm/internal.h:351!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 14732 Comm: kworker/u4:4 Not tainted 4.14.184-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: writeback wb_workfn (flush-8:0)
task: ffff88804d788180 task.stack: ffff888057420000
RIP: 0010:vma_address mm/internal.h:351 [inline]
RIP: 0010:rmap_walk_file+0x405/0x8a0 mm/rmap.c:1822
RSP: 0018:ffff8880574272b0 EFLAGS: 00010287
RAX: 0000000000000102 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff88804d788a80 RDI: ffffed100ae84e35
RBP: ffffea00020d4540 R08: 0000000000000102 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888000126da8
R13: dffffc0000000000 R14: ffff888057427388 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880aec00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020f7e000 CR3: 000000008528e000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
rmap_walk+0xe5/0x180 mm/rmap.c:1847
page_mkclean+0x148/0x180 mm/rmap.c:981
clear_page_dirty_for_io+0x1fa/0x7f0 mm/page-writeback.c:2704
mpage_submit_page+0x6e/0x220 fs/ext4/inode.c:2206
mpage_process_page_bufs+0x425/0x520 fs/ext4/inode.c:2336
mpage_prepare_extent_to_map+0x43e/0xa50 fs/ext4/inode.c:2708
ext4_writepages+0x1062/0x3000 fs/ext4/inode.c:2855
do_writepages+0xd0/0x250 mm/page-writeback.c:2361
__writeback_single_inode+0xda/0x1140 fs/fs-writeback.c:1367
writeback_sb_inodes+0x475/0xcf0 fs/fs-writeback.c:1631
wb_writeback+0x247/0xba0 fs/fs-writeback.c:1807
wb_do_writeback fs/fs-writeback.c:1939 [inline]
wb_workfn+0x2a8/0xe70 fs/fs-writeback.c:1975
process_one_work+0x7c0/0x14c0 kernel/workqueue.c:2116
worker_thread+0x5d7/0x1080 kernel/workqueue.c:2250
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
Code: 80 7c 24 3c 00 0f 84 01 03 00 00 48 83 c4 40 5b 5d 41 5c 41 5d 41 5e 41 5f e9 f8 a0 dd ff e8 f3 a0 dd ff 4c 89 e7 e8 87 7a fb ff <0f> 0b e8 e4 a0 dd ff 48 8b 44 24 20 4c 8d 68 68 4c 89 ef e8 43
RIP: vma_address mm/internal.h:351 [inline] RSP: ffff8880574272b0
RIP: rmap_walk_file+0x405/0x8a0 mm/rmap.c:1822 RSP: ffff8880574272b0
---[ end trace 2995597b3a8a455d ]---


---
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.

[syzbot]

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