KCSAN: data-race in inc_node_page_state / release_pages (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d5beb314 Merge tag 'hyperv-fixes-signed' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13c52f89500000
kernel config: https://syzkaller.appspot.com/x/.config?x=cf114765a0c30afa
dashboard link: https://syzkaller.appspot.com/bug?extid=4f8f4c7473715f690bbe
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project.git 913f6005669cfb590c99865a90bc51ed0983d09d)
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linu...@kvack.org]

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

==================================================================
BUG: KCSAN: data-race in inc_node_page_state / release_pages

write to 0xffffea0004472cc0 of 8 bytes by task 16140 on cpu 0:
instrument_write include/linux/instrumented.h:42 [inline]
__clear_bit include/asm-generic/bitops/instrumented-non-atomic.h:42 [inline]
__ClearPageLRU include/linux/page-flags.h:337 [inline]
release_pages+0x41c/0x8b0 mm/swap.c:940
__pagevec_release+0xa7/0xd0 mm/swap.c:972
pagevec_release include/linux/pagevec.h:88 [inline]
__invalidate_mapping_pages+0x6c6/0x720 mm/truncate.c:610
invalidate_mapping_pagevec+0x29/0x40 mm/truncate.c:647
generic_fadvise+0x432/0x480 mm/fadvise.c:157
vfs_fadvise mm/fadvise.c:186 [inline]
ksys_fadvise64_64 mm/fadvise.c:200 [inline]
__do_sys_fadvise64 mm/fadvise.c:215 [inline]
__se_sys_fadvise64 mm/fadvise.c:213 [inline]
__x64_sys_fadvise64+0xc5/0x100 mm/fadvise.c:213
do_syscall_64+0x39/0x80 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9

read to 0xffffea0004472cc0 of 8 bytes by task 3000 on cpu 1:
page_to_nid include/linux/mm.h:1302 [inline]
page_pgdat include/linux/mm.h:1449 [inline]
inc_node_page_state+0xe/0xc0 mm/vmstat.c:603
test_clear_page_writeback+0x3c7/0x450 mm/page-writeback.c:2766
end_page_writeback+0xa7/0x110 mm/filemap.c:1487
ext4_finish_bio+0x429/0x490 fs/ext4/page-io.c:146
ext4_release_io_end+0x98/0x200 fs/ext4/page-io.c:161
ext4_end_io_end fs/ext4/page-io.c:195 [inline]
ext4_do_flush_completed_IO fs/ext4/page-io.c:260 [inline]
ext4_end_io_rsv_work+0x306/0x360 fs/ext4/page-io.c:274
process_one_work+0x3e1/0x950 kernel/workqueue.c:2272
worker_thread+0x635/0xb90 kernel/workqueue.c:2418
kthread+0x1fd/0x220 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 3000 Comm: kworker/u4:3 Not tainted 5.10.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: ext4-rsv-conversion ext4_end_io_rsv_work
==================================================================


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