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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 52b1853b080a Merge tag 'i2c-for-6.7-final' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=107c1639e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=17e138c8fc533c5e
dashboard link: https://syzkaller.appspot.com/bug?extid=f9c103e0a0e42f036ac0
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/32436e2e6cf1/disk-52b1853b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c0a27bdf8e03/vmlinux-52b1853b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f165b88f9643/bzImage-52b1853b.xz

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

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

read-write to 0xffff888103b88058 of 8 bytes by interrupt on cpu 0:
dio_bio_end_io+0x53/0xd0 fs/direct-io.c:388
bio_endio+0x35f/0x400 block/bio.c:1603
req_bio_endio block/blk-mq.c:788 [inline]
blk_update_request+0x41c/0x950 block/blk-mq.c:933
blk_mq_end_request+0x26/0x50 block/blk-mq.c:1056
lo_complete_rq+0xce/0x170 drivers/block/loop.c:370
blk_complete_reqs block/blk-mq.c:1131 [inline]
blk_done_softirq+0x73/0xa0 block/blk-mq.c:1136
__do_softirq+0xc4/0x279 kernel/softirq.c:553
run_ksoftirqd+0x17/0x20 kernel/softirq.c:921
smpboot_thread_fn+0x30a/0x4a0 kernel/smpboot.c:164
kthread+0x1d7/0x210 kernel/kthread.c:388
ret_from_fork+0x48/0x60 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242

read to 0xffff888103b88058 of 8 bytes by task 22956 on cpu 1:
dio_bio_reap fs/direct-io.c:549 [inline]
dio_new_bio+0x249/0x410 fs/direct-io.c:668
dio_send_cur_page+0x1f2/0x790 fs/direct-io.c:749
submit_page_section+0x1a2/0x5a0 fs/direct-io.c:814
do_direct_IO fs/direct-io.c:1029 [inline]
__blockdev_direct_IO+0x1440/0x1f90 fs/direct-io.c:1248
blockdev_direct_IO include/linux/fs.h:3038 [inline]
fat_direct_IO+0x110/0x1d0 fs/fat/inode.c:283
generic_file_direct_write+0xab/0x1f0 mm/filemap.c:3852
__generic_file_write_iter+0xae/0x120 mm/filemap.c:4008
generic_file_write_iter+0x7d/0x1c0 mm/filemap.c:4048
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:52 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

value changed: 0xffff888148ff7840 -> 0xffff888148ff7b40

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 22956 Comm: syz-executor.4 Not tainted 6.7.0-rc8-syzkaller-00177-g52b1853b080a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/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.