[moderation] [ext4?] KCSAN: data-race in _copy_to_iter / string (6)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6916d5703ddf Merge tag 'drm-fixes-2026-05-16' of https://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1754e02e580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2e40c0f41e01837e
dashboard link: https://syzkaller.appspot.com/bug?extid=d12abd0fb4758872a29b
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
CC: [adilger...@dilger.ca ja...@suse.cz liba...@linux.alibaba.com linux...@vger.kernel.org linux-...@vger.kernel.org oja...@linux.ibm.com rites...@gmail.com ty...@mit.edu yi.z...@huawei.com]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/68f41c193b0d/disk-6916d570.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b43a9332252c/vmlinux-6916d570.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6d9ea22a0feb/bzImage-6916d570.xz

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

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

write to 0xffff888177489050 of 1 bytes by task 12619 on cpu 0:
string_nocheck lib/vsprintf.c:659 [inline]
string+0x187/0x220 lib/vsprintf.c:737
bdev_name+0xd7/0x2b0 lib/vsprintf.c:977
pointer+0x549/0xcb0 lib/vsprintf.c:2588
vsnprintf+0x491/0x860 lib/vsprintf.c:2952
snprintf+0x86/0xb0 lib/vsprintf.c:3042
ext4_multi_mount_protect+0x4e4/0x600 fs/ext4/mmp.c:382
__ext4_fill_super fs/ext4/super.c:5497 [inline]
ext4_fill_super+0x22e6/0x37c0 fs/ext4/super.c:5824
get_tree_bdev_flags+0x291/0x300 fs/super.c:1694
get_tree_bdev+0x1f/0x30 fs/super.c:1717
ext4_get_tree+0x1c/0x30 fs/ext4/super.c:5856
vfs_get_tree+0x57/0x1d0 fs/super.c:1754
fc_mount fs/namespace.c:1193 [inline]
do_new_mount_fc fs/namespace.c:3758 [inline]
do_new_mount+0x288/0x8d0 fs/namespace.c:3834
path_mount+0x4d0/0xbc0 fs/namespace.c:4154
do_mount fs/namespace.c:4167 [inline]
__do_sys_mount fs/namespace.c:4383 [inline]
__se_sys_mount+0x28c/0x2e0 fs/namespace.c:4360
__x64_sys_mount+0x67/0x80 fs/namespace.c:4360
x64_sys_call+0x2d61/0x3020 arch/x86/include/generated/asm/syscalls_64.h:166
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x12c/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff888177489000 of 512 bytes by task 6425 on cpu 1:
instrument_copy_to_user include/linux/instrumented.h:130 [inline]
copy_to_user_iter lib/iov_iter.c:24 [inline]
iterate_ubuf include/linux/iov_iter.h:30 [inline]
iterate_and_advance2 include/linux/iov_iter.h:302 [inline]
iterate_and_advance include/linux/iov_iter.h:330 [inline]
_copy_to_iter+0x130/0xea0 lib/iov_iter.c:197
copy_page_to_iter+0x178/0x210 lib/iov_iter.c:374
copy_folio_to_iter include/linux/uio.h:204 [inline]
filemap_read+0x407/0xa10 mm/filemap.c:2857
blkdev_read_iter+0x22d/0x2e0 block/fops.c:855
new_sync_read fs/read_write.c:493 [inline]
vfs_read+0x6c0/0x7f0 fs/read_write.c:574
ksys_read+0xdc/0x1a0 fs/read_write.c:717
__do_sys_read fs/read_write.c:726 [inline]
__se_sys_read fs/read_write.c:724 [inline]
__x64_sys_read+0x40/0x50 fs/read_write.c:724
x64_sys_call+0x2886/0x3020 arch/x86/include/generated/asm/syscalls_64.h:1
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x12c/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 6425 Comm: udevd Tainted: G W syzkaller #0 PREEMPT(full)
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
==================================================================


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