[moderation] [block?] KCSAN: data-race in bdev_statx / queue_limits_commit_update

Hello,

syzbot found the following issue on:

HEAD commit: d76bb1ebb558 Merge tag 'erofs-for-6.15-rc6-fixes' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=127de4f4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6154604431d9aaf9
dashboard link: https://syzkaller.appspot.com/bug?extid=7cafee44d163891ef288
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
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/7e7bc51b8794/disk-d76bb1eb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a11c96da2812/vmlinux-d76bb1eb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ed68c1372e5a/bzImage-d76bb1eb.xz

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

==================================================================
BUG: KCSAN: data-race in bdev_statx / queue_limits_commit_update

read to 0xffff888101e3cbf8 of 4 bytes by task 3511 on cpu 1:
queue_io_min include/linux/blkdev.h:1313 [inline]
bdev_io_min include/linux/blkdev.h:1318 [inline]
bdev_statx+0x293/0x2d0 block/bdev.c:1341
vfs_getattr_nosec+0x1b6/0x1e0 fs/stat.c:224
vfs_getattr fs/stat.c:259 [inline]
vfs_fstat fs/stat.c:278 [inline]
__do_sys_newfstat fs/stat.c:546 [inline]
__se_sys_newfstat+0xa4/0x2d0 fs/stat.c:543
__x64_sys_newfstat+0x31/0x40 fs/stat.c:543
x64_sys_call+0x27e1/0x2fb0 arch/x86/include/generated/asm/syscalls_64.h:6
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd0/0x1a0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

write to 0xffff888101e3cbb8 of 176 bytes by task 3519 on cpu 0:
queue_limits_commit_update+0x4c/0x110 block/blk-settings.c:461
loop_configure+0x746/0x9f0 drivers/block/loop.c:1029
lo_ioctl+0x5f8/0x1560 drivers/block/loop.c:-1
blkdev_ioctl+0x34f/0x440 block/ioctl.c:704
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:906 [inline]
__se_sys_ioctl+0xcb/0x140 fs/ioctl.c:892
__x64_sys_ioctl+0x43/0x50 fs/ioctl.c:892
x64_sys_call+0x19a8/0x2fb0 arch/x86/include/generated/asm/syscalls_64.h:17
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd0/0x1a0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 3519 Comm: syz.3.25 Not tainted 6.15.0-rc5-syzkaller-00043-gd76bb1ebb558 #0 PREEMPT(voluntary)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
==================================================================
loop3: detected capacity change from 0 to 512
EXT4-fs (loop3): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: writeback.
ext4 filesystem being mounted at /3/bus supports timestamps until 2038-01-19 (0x7fffffff)
EXT4-fs error (device loop3): ext4_do_update_inode:5211: inode #2: comm syz.3.25: corrupted inode contents
EXT4-fs error (device loop3): ext4_dirty_inode:6103: inode #2: comm syz.3.25: mark_inode_dirty error
EXT4-fs error (device loop3): ext4_do_update_inode:5211: inode #2: comm syz.3.25: corrupted inode contents
EXT4-fs error (device loop3): __ext4_ext_dirty:207: inode #2: comm syz.3.25: mark_inode_dirty error


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