[moderation] [mm?] KCSAN: data-race in __lru_add_drain_all / deactivate_file_folio (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 49a73b1652c5 Merge tag 'firewire-fixes-6.9-rc6' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14d8c2f8980000
kernel config: https://syzkaller.appspot.com/x/.config?x=c3beef2aff822313
dashboard link: https://syzkaller.appspot.com/bug?extid=25946262c3a67c5c25ee
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/869474934b87/disk-49a73b16.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d7e932324bfd/vmlinux-49a73b16.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c2aedff3b667/bzImage-49a73b16.xz

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

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

read-write to 0xffff888237d2ad08 of 1 bytes by task 3793 on cpu 1:
folio_batch_add include/linux/pagevec.h:77 [inline]
folio_batch_add_and_move mm/swap.c:246 [inline]
deactivate_file_folio+0x66/0x160 mm/swap.c:716
mapping_try_invalidate+0x2be/0x3e0 mm/truncate.c:518
invalidate_mapping_pages+0x27/0x40 mm/truncate.c:549
invalidate_bdev+0x65/0x80 block/bdev.c:96
ext4_put_super+0x51b/0x7e0 fs/ext4/super.c:1361
generic_shutdown_super+0xde/0x210 fs/super.c:641
kill_block_super+0x2a/0x70 fs/super.c:1675
ext4_kill_sb+0x44/0x80 fs/ext4/super.c:7327
deactivate_locked_super+0x7d/0x1c0 fs/super.c:472
deactivate_super+0x9f/0xb0 fs/super.c:505
cleanup_mnt+0x272/0x2e0 fs/namespace.c:1267
__cleanup_mnt+0x19/0x20 fs/namespace.c:1274
task_work_run+0x13a/0x1a0 kernel/task_work.c:180
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0xbe/0x130 kernel/entry/common.c:218
do_syscall_64+0xda/0x1d0 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff888237d2ad08 of 1 bytes by task 3776 on cpu 0:
folio_batch_count include/linux/pagevec.h:56 [inline]
cpu_needs_drain mm/swap.c:812 [inline]
__lru_add_drain_all+0x1a2/0x420 mm/swap.c:904
lru_add_drain_all+0x10/0x20 mm/swap.c:920
invalidate_bdev+0x54/0x80 block/bdev.c:95
ext4_put_super+0x51b/0x7e0 fs/ext4/super.c:1361
generic_shutdown_super+0xde/0x210 fs/super.c:641
kill_block_super+0x2a/0x70 fs/super.c:1675
ext4_kill_sb+0x44/0x80 fs/ext4/super.c:7327
deactivate_locked_super+0x7d/0x1c0 fs/super.c:472
deactivate_super+0x9f/0xb0 fs/super.c:505
cleanup_mnt+0x272/0x2e0 fs/namespace.c:1267
__cleanup_mnt+0x19/0x20 fs/namespace.c:1274
task_work_run+0x13a/0x1a0 kernel/task_work.c:180
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0xbe/0x130 kernel/entry/common.c:218
do_syscall_64+0xda/0x1d0 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x01 -> 0x02

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 3776 Comm: syz-executor.4 Not tainted 6.9.0-rc6-syzkaller-00113-g49a73b1652c5 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
==================================================================
EXT4-fs (loop4): unmounting filesystem 00000000-0000-0000-0000-000000000000.


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