[moderation] [mm?] KCSAN: data-race in __filemap_remove_folio / file_write_and_wait_range (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: eb3479bc23fa Merge tag 'kbuild-fixes-v6.7' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14ee43d4e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=a91f789b98394377
dashboard link: https://syzkaller.appspot.com/bug?extid=78a4549691c135a19330
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/2b7b64012dfb/disk-eb3479bc.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fc10d7369a4b/vmlinux-eb3479bc.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1be851c4aeea/bzImage-eb3479bc.xz

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

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

read-write to 0xffff888100633130 of 8 bytes by task 16710 on cpu 0:
page_cache_delete mm/filemap.c:144 [inline]
__filemap_remove_folio+0x1d1/0x2d0 mm/filemap.c:222
__remove_mapping+0x341/0x460 mm/vmscan.c:756
remove_mapping+0x22/0x90 mm/vmscan.c:789
mapping_evict_folio mm/truncate.c:281 [inline]
mapping_try_invalidate+0x286/0x3d0 mm/truncate.c:520
invalidate_mapping_pages+0x27/0x30 mm/truncate.c:558
invalidate_bdev+0x65/0x70 block/bdev.c:87
bdev_disk_changed+0x118/0xc70 block/partitions/core.c:664
loop_reread_partitions drivers/block/loop.c:518 [inline]
loop_set_status+0x4ab/0x550 drivers/block/loop.c:1322
lo_ioctl+0x892/0x12e0
blkdev_ioctl+0x375/0x460 block/ioctl.c:633
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:871 [inline]
__se_sys_ioctl+0xcf/0x140 fs/ioctl.c:857
__x64_sys_ioctl+0x43/0x50 fs/ioctl.c:857
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

read to 0xffff888100633130 of 8 bytes by task 16592 on cpu 1:
mapping_needs_writeback mm/filemap.c:625 [inline]
file_write_and_wait_range+0x67/0x190 mm/filemap.c:777
blkdev_fsync+0x4e/0xa0 block/fops.c:529
vfs_fsync_range+0x111/0x120 fs/sync.c:188
generic_write_sync+0xf2/0x120 include/linux/fs.h:2653
blkdev_write_iter+0x364/0x390 block/fops.c:700
do_iter_write+0x4ad/0x770 fs/read_write.c:860
vfs_iter_write+0x56/0x70 fs/read_write.c:901
iter_file_splice_write+0x462/0x7e0 fs/splice.c:736
do_splice_from fs/splice.c:933 [inline]
direct_splice_actor+0x8a/0xb0 fs/splice.c:1142
splice_direct_to_actor+0x31d/0x690 fs/splice.c:1088
do_splice_direct+0x10d/0x190 fs/splice.c:1194
do_sendfile+0x3c4/0x980 fs/read_write.c:1254
__do_sys_sendfile64 fs/read_write.c:1322 [inline]
__se_sys_sendfile64 fs/read_write.c:1308 [inline]
__x64_sys_sendfile64+0x110/0x150 fs/read_write.c:1308
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: 0x00000000000000b1 -> 0x00000000000000ae

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 16592 Comm: syz-executor.2 Not tainted 6.7.0-rc1-syzkaller-00366-geb3479bc23fa #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.