[moderation] [mm?] KCSAN: data-race in __lru_add_drain_all / folio_batch_move_lru

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f1a09972a45a Merge tag 'ata-6.7-rc3' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=165c99cce80000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c1151391aefc0c3
dashboard link: https://syzkaller.appspot.com/bug?extid=9a4849f7d9be64405853
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linu...@kvack.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/dffb0d99ad2d/disk-f1a09972.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/080ad4a9580e/vmlinux-f1a09972.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f1ac25646188/bzImage-f1a09972.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9a4849...@syzkaller.appspotmail.com

==================================================================
BUG: KCSAN: data-race in __lru_add_drain_all / folio_batch_move_lru

write to 0xffff888237c29988 of 1 bytes by task 2793 on cpu 0:
folio_batch_reinit include/linux/pagevec.h:48 [inline]
folio_batch_move_lru+0x2bf/0x2f0 mm/swap.c:225
folio_batch_add_and_move mm/swap.c:234 [inline]
folio_add_lru mm/swap.c:517 [inline]
folio_add_lru_vma+0xf4/0x160 mm/swap.c:537
wp_page_copy mm/memory.c:3189 [inline]
do_wp_page+0x10f8/0x1f40 mm/memory.c:3510
handle_pte_fault mm/memory.c:5054 [inline]
__handle_mm_fault mm/memory.c:5179 [inline]
handle_mm_fault+0xe5d/0x2dd0 mm/memory.c:5344
do_user_addr_fault arch/x86/mm/fault.c:1413 [inline]
handle_page_fault arch/x86/mm/fault.c:1505 [inline]
exc_page_fault+0x2f7/0x6c0 arch/x86/mm/fault.c:1561
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570

read to 0xffff888237c29988 of 1 bytes by task 2785 on cpu 1:
folio_batch_count include/linux/pagevec.h:53 [inline]
cpu_needs_drain mm/swap.c:795 [inline]
__lru_add_drain_all+0x137/0x420 mm/swap.c:889
lru_add_drain_all+0x10/0x20 mm/swap.c:905
invalidate_bdev+0x54/0x70 block/bdev.c:86
__ext4_fill_super fs/ext4/super.c:5687 [inline]
ext4_fill_super+0x1789/0x39a0 fs/ext4/super.c:5712
get_tree_bdev+0x272/0x300 fs/super.c:1598
ext4_get_tree+0x1c/0x20 fs/ext4/super.c:5744
vfs_get_tree+0x51/0x1b0 fs/super.c:1771
do_new_mount+0x203/0x660 fs/namespace.c:3337
path_mount+0x496/0xb30 fs/namespace.c:3664
do_mount fs/namespace.c:3677 [inline]
__do_sys_mount fs/namespace.c:3886 [inline]
__se_sys_mount+0x27f/0x2d0 fs/namespace.c:3863
__x64_sys_mount+0x67/0x80 fs/namespace.c:3863
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x0f -> 0x00

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 2785 Comm: syz-executor.4 Tainted: G W 6.7.0-rc2-syzkaller-00147-gf1a09972a45a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
==================================================================


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

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

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