[moderation] [exfat?] KCSAN: data-race in dio_bio_end_io / dio_new_bio (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 59dbb9d81adf Merge tag 'xsa465+xsa466-6.13-tag' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13640cf8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=67aa69407438e9cf
dashboard link: https://syzkaller.appspot.com/bug?extid=a7fee2680bad8ac961c0
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/e6abad5b3136/disk-59dbb9d8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1e89a5d7ffd4/vmlinux-59dbb9d8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6cfd8d142bde/bzImage-59dbb9d8.xz

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

==================================================================
BUG: KCSAN: data-race in dio_bio_end_io / dio_new_bio

read-write to 0xffff888109232058 of 8 bytes by interrupt on cpu 0:
dio_bio_end_io+0x53/0xd0 fs/direct-io.c:387
bio_endio+0x369/0x410 block/bio.c:1645
blk_update_request+0x368/0x860 block/blk-mq.c:981
blk_mq_end_request+0x26/0x50 block/blk-mq.c:1143
lo_complete_rq+0xce/0x180 drivers/block/loop.c:386
blk_complete_reqs block/blk-mq.c:1218 [inline]
blk_done_softirq+0x74/0xb0 block/blk-mq.c:1223
handle_softirqs+0xbf/0x280 kernel/softirq.c:561
run_ksoftirqd+0x1c/0x30 kernel/softirq.c:950
smpboot_thread_fn+0x31c/0x4c0 kernel/smpboot.c:164
kthread+0x1d1/0x210 kernel/kthread.c:389
ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

read to 0xffff888109232058 of 8 bytes by task 5482 on cpu 1:
dio_bio_reap fs/direct-io.c:550 [inline]
dio_new_bio+0x249/0x460 fs/direct-io.c:669
dio_send_cur_page+0x1f2/0x7a0 fs/direct-io.c:750
submit_page_section+0x1a3/0x5b0 fs/direct-io.c:815
do_direct_IO fs/direct-io.c:1030 [inline]
__blockdev_direct_IO+0x11bb/0x1e80 fs/direct-io.c:1243
blockdev_direct_IO include/linux/fs.h:3313 [inline]
fat_direct_IO+0x10a/0x1d0 fs/fat/inode.c:281
generic_file_direct_write+0xf7/0x250 mm/filemap.c:3978
__generic_file_write_iter+0xae/0x120 mm/filemap.c:4142
generic_file_write_iter+0x77/0x1c0 mm/filemap.c:4182
do_iter_readv_writev+0x394/0x450
vfs_writev+0x2d4/0x880 fs/read_write.c:1050
do_pwritev fs/read_write.c:1146 [inline]
__do_sys_pwritev2 fs/read_write.c:1204 [inline]
__se_sys_pwritev2+0x100/0x1c0 fs/read_write.c:1195
__x64_sys_pwritev2+0x78/0x90 fs/read_write.c:1195
x64_sys_call+0x2afe/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:329
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xc9/0x1c0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0xffff88811a8d4540 -> 0xffff88811833cf00

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 5482 Comm: syz.4.795 Not tainted 6.13.0-rc3-syzkaller-00026-g59dbb9d81adf #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024
==================================================================


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