[moderation] [fs?] KCSAN: data-race in pipe_release / pipe_wait_readable (7)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e0cce98fe279 Merge tag 'tpmdd-next-6.10-rc2' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=150e5ad2980000
kernel config: https://syzkaller.appspot.com/x/.config?x=b639694183430f97
dashboard link: https://syzkaller.appspot.com/bug?extid=6952cc4f22a1dee3c9bb
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [bra...@kernel.org ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d842c66d71ef/disk-e0cce98f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d6549d16a1a0/vmlinux-e0cce98f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fa3ddb2c67c0/bzImage-e0cce98f.xz

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

==================================================================
BUG: KCSAN: data-race in pipe_release / pipe_wait_readable

read-write to 0xffff8881337e136c of 4 bytes by task 12081 on cpu 1:
put_pipe_info fs/pipe.c:712 [inline]
pipe_release+0x164/0x1c0 fs/pipe.c:742
__fput+0x2c2/0x660 fs/file_table.c:422
__fput_sync+0x44/0x60 fs/file_table.c:507
__do_sys_close fs/open.c:1555 [inline]
__se_sys_close+0x101/0x1b0 fs/open.c:1540
__x64_sys_close+0x1f/0x30 fs/open.c:1540
x64_sys_call+0x25f1/0x2d70 arch/x86/include/generated/asm/syscalls_64.h:4
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 0xffff8881337e136c of 4 bytes by task 12082 on cpu 0:
pipe_lock fs/pipe.c:91 [inline]
pipe_wait_readable+0x1ec/0x240 fs/pipe.c:1061
splice_from_pipe_next+0x24f/0x390 fs/splice.c:548
__splice_from_pipe+0xb0/0x4b0 fs/splice.c:609
vmsplice_to_user fs/splice.c:1524 [inline]
__do_sys_vmsplice fs/splice.c:1626 [inline]
__se_sys_vmsplice+0x265/0xdc0 fs/splice.c:1598
__x64_sys_vmsplice+0x55/0x70 fs/splice.c:1598
x64_sys_call+0xb5f/0x2d70 arch/x86/include/generated/asm/syscalls_64.h:279
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: 0x00000002 -> 0x00000001

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 12082 Comm: syz-executor.0 Not tainted 6.10.0-rc1-syzkaller-00021-ge0cce98fe279 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/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