[moderation] [block?] KCSAN: data-race in __kernel_write_iter / set_task_ioprio

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d12937763990 Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16618287980000
kernel config: https://syzkaller.appspot.com/x/.config?x=91af2aaf073838b1
dashboard link: https://syzkaller.appspot.com/bug?extid=cf58a5c9bd44f4f17a33
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [ax...@kernel.dk linux...@vger.kernel.org linux-...@vger.kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/84049b9d0a23/disk-d1293776.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/36e0699c1f10/vmlinux-d1293776.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4a9bb89ead25/bzImage-d1293776.xz

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

==================================================================
BUG: KCSAN: data-race in __kernel_write_iter / set_task_ioprio

write to 0xffff88810148ba38 of 8 bytes by task 6014 on cpu 0:
set_task_ioprio+0x240/0x260 block/blk-ioc.c:287
__do_sys_ioprio_set block/ioprio.c:125 [inline]
__se_sys_ioprio_set+0x246/0x580 block/ioprio.c:69
__x64_sys_ioprio_set+0x43/0x50 block/ioprio.c:69
x64_sys_call+0x2bcf/0x2d60 arch/x86/include/generated/asm/syscalls_64.h:252
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

read to 0xffff88810148ba38 of 8 bytes by task 6024 on cpu 1:
__get_task_ioprio include/linux/ioprio.h:59 [inline]
get_current_ioprio include/linux/ioprio.h:83 [inline]
init_sync_kiocb include/linux/fs.h:2345 [inline]
__kernel_write_iter+0xe8/0x4e0 fs/read_write.c:614
dump_emit_page fs/coredump.c:884 [inline]
dump_user_range+0x3a7/0x550 fs/coredump.c:945
elf_core_dump+0x1b66/0x1c60 fs/binfmt_elf.c:2121
do_coredump+0x1736/0x1ce0 fs/coredump.c:758
get_signal+0xdc0/0x1070 kernel/signal.c:2902
arch_do_signal_or_restart+0x95/0x4b0 arch/x86/kernel/signal.c:337
exit_to_user_mode_loop kernel/entry/common.c:111 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
irqentry_exit_to_user_mode+0x9a/0x130 kernel/entry/common.c:231
irqentry_exit+0x12/0x50 kernel/entry/common.c:334
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623

value changed: 0x0000000000000000 -> 0xffff88810121e170

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 6024 Comm: syz.3.753 Not tainted 6.12.0-rc4-syzkaller-00045-gd12937763990 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/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.