[moderation] [exfat?] KCSAN: data-race in _copy_to_iter / fat12_ent_put (6)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e326df53af00 Merge tag 'v6.8-p5' of git://git.kernel.org/p..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1535b2ca180000
kernel config: https://syzkaller.appspot.com/x/.config?x=53006d590acdf777
dashboard link: https://syzkaller.appspot.com/bug?extid=41adf9094596bdc751c0
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [hiro...@mail.parknet.co.jp linki...@kernel.org linux-...@vger.kernel.org linux-...@vger.kernel.org sj155...@samsung.com]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/442bc7bab3d5/disk-e326df53.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/16e72f8e2855/vmlinux-e326df53.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7433e48b60ff/bzImage-e326df53.xz

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

==================================================================
BUG: KCSAN: data-race in _copy_to_iter / fat12_ent_put

read-write to 0xffff88813dfb8210 of 1 bytes by task 6838 on cpu 0:
fat12_ent_put+0xcc/0x180 fs/fat/fatent.c:165
fat_alloc_clusters+0x4b5/0xa60 fs/fat/fatent.c:503
fat_add_cluster fs/fat/inode.c:108 [inline]
__fat_get_block fs/fat/inode.c:155 [inline]
fat_get_block+0x25c/0x5e0 fs/fat/inode.c:190
__block_write_begin_int+0x40b/0xf80 fs/buffer.c:2103
__block_write_begin fs/buffer.c:2152 [inline]
block_write_begin+0x7b/0x170 fs/buffer.c:2211
cont_write_begin+0x479/0x690 fs/buffer.c:2565
fat_write_begin+0x61/0xf0 fs/fat/inode.c:230
generic_perform_write+0x1c9/0x410 mm/filemap.c:3930
__generic_file_write_iter+0xa1/0x120 mm/filemap.c:4025
generic_file_write_iter+0x7d/0x1c0 mm/filemap.c:4051
do_iter_readv_writev+0x2b0/0x330
vfs_writev+0x2e9/0x860 fs/read_write.c:971
do_pwritev fs/read_write.c:1072 [inline]
__do_sys_pwritev2 fs/read_write.c:1131 [inline]
__se_sys_pwritev2+0x10c/0x1d0 fs/read_write.c:1122
__x64_sys_pwritev2+0x78/0x90 fs/read_write.c:1122
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

read to 0xffff88813dfb8000 of 1024 bytes by task 3372 on cpu 1:
instrument_copy_to_user include/linux/instrumented.h:113 [inline]
copy_to_user_iter lib/iov_iter.c:24 [inline]
iterate_ubuf include/linux/iov_iter.h:29 [inline]
iterate_and_advance2 include/linux/iov_iter.h:245 [inline]
iterate_and_advance include/linux/iov_iter.h:271 [inline]
_copy_to_iter+0x126/0xb20 lib/iov_iter.c:186
copy_page_to_iter+0x171/0x2b0 lib/iov_iter.c:381
copy_folio_to_iter include/linux/uio.h:181 [inline]
filemap_read+0x42c/0x680 mm/filemap.c:2654
blkdev_read_iter+0x217/0x2c0 block/fops.c:757
call_read_iter include/linux/fs.h:2081 [inline]
new_sync_read fs/read_write.c:395 [inline]
vfs_read+0x5ab/0x6a0 fs/read_write.c:476
ksys_read+0xeb/0x1a0 fs/read_write.c:619
__do_sys_read fs/read_write.c:629 [inline]
__se_sys_read fs/read_write.c:627 [inline]
__x64_sys_read+0x42/0x50 fs/read_write.c:627
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 3372 Comm: udevd Not tainted 6.8.0-rc6-syzkaller-00024-ge326df53af00 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
==================================================================
I/O error, dev loop2, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
I/O error, dev loop1, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
I/O error, dev loop4, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
I/O error, dev loop4, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Buffer I/O error on dev loop4, logical block 0, async page read


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