KASAN: wild-memory-access Write in page_vma_mapped_walk

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 205a42ce Linux 4.19.135
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=142ab74c900000
kernel config: https://syzkaller.appspot.com/x/.config?x=155b0b328eb5e700
dashboard link: https://syzkaller.appspot.com/bug?extid=60c5f2ecf824e2ac6168
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+60c5f2...@syzkaller.appspotmail.com

==================================================================
BUG: KASAN: wild-memory-access in atomic_inc include/asm-generic/atomic-instrumented.h:109 [inline]
BUG: KASAN: wild-memory-access in __lock_acquire+0x251/0x3ff0 kernel/locking/lockdep.c:3307
Write of size 4 at addr 00777770077001af by task kworker/u4:1/9181

CPU: 1 PID: 9181 Comm: kworker/u4:1 Not tainted 4.19.135-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: writeback wb_workfn (flush-8:0)
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
kasan_report_error.cold+0x15b/0x1c7 mm/kasan/report.c:352
kasan_report+0x8f/0x96 mm/kasan/report.c:412
atomic_inc include/asm-generic/atomic-instrumented.h:109 [inline]
__lock_acquire+0x251/0x3ff0 kernel/locking/lockdep.c:3307
lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3907
__raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
_raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:144
spin_lock include/linux/spinlock.h:329 [inline]
map_pte mm/page_vma_mapped.c:51 [inline]
page_vma_mapped_walk+0x1484/0x2240 mm/page_vma_mapped.c:213
page_mkclean_one+0x23e/0x5b0 mm/rmap.c:902
rmap_walk_file+0x4fe/0xc10 mm/rmap.c:1887
rmap_walk+0x105/0x190 mm/rmap.c:1905
page_mkclean+0x20f/0x2b0 mm/rmap.c:984
clear_page_dirty_for_io+0x305/0xee0 mm/page-writeback.c:2687
mpage_submit_page+0x80/0x250 fs/ext4/inode.c:2207
mpage_process_page_bufs+0x534/0x630 fs/ext4/inode.c:2337
mpage_prepare_extent_to_map+0x9a2/0xf10 fs/ext4/inode.c:2699
ext4_writepages+0x111d/0x37f0 fs/ext4/inode.c:2827
do_writepages+0xe5/0x290 mm/page-writeback.c:2344
__writeback_single_inode+0x113/0x1340 fs/fs-writeback.c:1371
writeback_sb_inodes+0x5a7/0x13c0 fs/fs-writeback.c:1635
__writeback_inodes_wb+0xc6/0x350 fs/fs-writeback.c:1704
wb_writeback+0x841/0xcc0 fs/fs-writeback.c:1813
wb_check_background_flush fs/fs-writeback.c:1881 [inline]
wb_do_writeback fs/fs-writeback.c:1969 [inline]
wb_workfn+0xb20/0x12f0 fs/fs-writeback.c:1997
process_one_work+0x864/0x1570 kernel/workqueue.c:2155
worker_thread+0x64c/0x1130 kernel/workqueue.c:2298
kthread+0x30b/0x410 kernel/kthread.c:246
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
==================================================================


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