[moderation] [mm?] KCSAN: data-race in __filemap_remove_folio / invalidate_bdev

Hello,

syzbot found the following issue on:

HEAD commit: 8560697b23dc Merge tag '6.15-rc2-smb3-client-fixes' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=115f64cc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=29bf2e4c55556614
dashboard link: https://syzkaller.appspot.com/bug?extid=966e25aa97f0900d18a4
compiler: Debian clang version 15.0.6, Debian LLD 15.0.6
CC: [[email protected] [email protected] [email protected]]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/bf9acb1b9880/disk-8560697b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/47dbe4c025da/vmlinux-8560697b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/74ec1aa5b269/bzImage-8560697b.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

==================================================================
BUG: KCSAN: data-race in __filemap_remove_folio / invalidate_bdev

read-write to 0xffff8881004c11f0 of 8 bytes by task 16440 on cpu 0:
page_cache_delete mm/filemap.c:146 [inline]
__filemap_remove_folio+0x1c7/0x2c0 mm/filemap.c:224
__remove_mapping+0x33f/0x470 mm/vmscan.c:813
remove_mapping+0x22/0x90 mm/vmscan.c:846
mapping_evict_folio mm/truncate.c:310 [inline]
mapping_try_invalidate+0x267/0x3f0 mm/truncate.c:531
invalidate_mapping_pages+0x27/0x40 mm/truncate.c:573
invalidate_bdev+0x58/0x70 block/bdev.c:102
loop_set_status+0x12b/0x5d0 drivers/block/loop.c:1211
lo_ioctl+0x81a/0x15e0 drivers/block/loop.c:-1
blkdev_ioctl+0x35b/0x450 block/ioctl.c:698
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:906 [inline]
__se_sys_ioctl+0xc9/0x140 fs/ioctl.c:892
__x64_sys_ioctl+0x43/0x50 fs/ioctl.c:892
x64_sys_call+0x168d/0x2e10 arch/x86/include/generated/asm/syscalls_64.h:17
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xc9/0x1a0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff8881004c11f0 of 8 bytes by task 15547 on cpu 1:
invalidate_bdev+0x25/0x70 block/bdev.c:99
bdev_disk_changed+0xe1/0xcd0 block/partitions/core.c:657
blkdev_get_whole+0x1eb/0x2d0 block/bdev.c:710
bdev_open+0x289/0x860 block/bdev.c:919
blkdev_open+0x258/0x290 block/fops.c:652
do_dentry_open+0x621/0xa20 fs/open.c:956
vfs_open+0x38/0x1e0 fs/open.c:1086
do_open fs/namei.c:3845 [inline]
path_openat+0x1b1c/0x2000 fs/namei.c:4004
do_filp_open+0x115/0x240 fs/namei.c:4031
do_sys_openat2+0xaa/0x110 fs/open.c:1429
do_sys_open fs/open.c:1444 [inline]
__do_sys_openat fs/open.c:1460 [inline]
__se_sys_openat fs/open.c:1455 [inline]
__x64_sys_openat+0xf8/0x120 fs/open.c:1455
x64_sys_call+0x1ac/0x2e10 arch/x86/include/generated/asm/syscalls_64.h:258
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xc9/0x1a0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x00000000000005c0 -> 0x00000000000005ba

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 15547 Comm: syz-executor Not tainted 6.15.0-rc2-syzkaller-00404-g8560697b23dc #0 PREEMPT(voluntary)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
==================================================================


---
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 [email protected].

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