[moderation] [mm?] KCSAN: data-race in __lru_add_drain_all / folio_activate (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 5e3f5b81de80 Merge tag 'net-6.7-rc5' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14f79382e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ac34c1f29a8029df
dashboard link: https://syzkaller.appspot.com/bug?extid=826d41fb803b4ea117d6
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/8894c209e25f/disk-5e3f5b81.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/42757ce1a7da/vmlinux-5e3f5b81.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a3314e0b4681/bzImage-5e3f5b81.xz

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

EXT4-fs (loop1): get orphan inode failed
EXT4-fs (loop1): mount failed
==================================================================
BUG: KCSAN: data-race in __lru_add_drain_all / folio_activate

read-write to 0xffff888237c29b88 of 1 bytes by task 2372 on cpu 0:
folio_batch_add include/linux/pagevec.h:74 [inline]
folio_batch_add_and_move mm/swap.c:231 [inline]
folio_activate+0xc0/0x1c0 mm/swap.c:361
folio_mark_accessed+0x119/0x190 mm/swap.c:481
shmem_file_read_iter+0x2d1/0x550 mm/shmem.c:2819
do_iter_read+0x4af/0x780 fs/read_write.c:795
vfs_iter_read+0x56/0x70 fs/read_write.c:837
lo_read_simple drivers/block/loop.c:290 [inline]
do_req_filebacked drivers/block/loop.c:500 [inline]
loop_handle_cmd drivers/block/loop.c:1915 [inline]
loop_process_work+0x98c/0x12e0 drivers/block/loop.c:1950
loop_workfn+0x31/0x40 drivers/block/loop.c:1974
process_one_work kernel/workqueue.c:2627 [inline]
process_scheduled_works+0x5b8/0xa30 kernel/workqueue.c:2700
worker_thread+0x525/0x730 kernel/workqueue.c:2781
kthread+0x1d7/0x210 kernel/kthread.c:388
ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242

read to 0xffff888237c29b88 of 1 bytes by task 5620 on cpu 1:
folio_batch_count include/linux/pagevec.h:53 [inline]
cpu_needs_drain mm/swap.c:800 [inline]
__lru_add_drain_all+0x21d/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:52 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0x00 -> 0x01

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 5620 Comm: syz-executor.1 Not tainted 6.7.0-rc4-syzkaller-00111-g5e3f5b81de80 #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.