[moderation] [fs?] KCSAN: data-race in pipe_lock / pipe_release (12)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: fbafc3e621c3 Merge tag 'for_linus' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=137623c9e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=601ed47d1ac58cea
dashboard link: https://syzkaller.appspot.com/bug?extid=58f9471378c38316b5a2
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [bra...@kernel.org 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/4bf9d6e749f0/disk-fbafc3e6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f710db8f545b/vmlinux-fbafc3e6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1099657ded40/bzImage-fbafc3e6.xz

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

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

read-write to 0xffff88814627a66c of 4 bytes by task 13853 on cpu 1:
put_pipe_info fs/pipe.c:715 [inline]
pipe_release+0x164/0x1c0 fs/pipe.c:745
__fput+0x299/0x630 fs/file_table.c:394
__fput_sync+0x44/0x50 fs/file_table.c:475
__do_sys_close fs/open.c:1587 [inline]
__se_sys_close+0xfa/0x1a0 fs/open.c:1572
__x64_sys_close+0x1f/0x30 fs/open.c:1572
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

read to 0xffff88814627a66c of 4 bytes by task 13957 on cpu 0:
pipe_lock_nested fs/pipe.c:81 [inline]
pipe_lock+0x17/0x40 fs/pipe.c:90
splice_to_socket+0x7e/0x9c0 fs/splice.c:801
do_splice_from fs/splice.c:933 [inline]
do_splice+0x99d/0x10a0 fs/splice.c:1292
__do_splice fs/splice.c:1370 [inline]
__do_sys_splice fs/splice.c:1586 [inline]
__se_sys_splice+0x24c/0x380 fs/splice.c:1568
__x64_sys_splice+0x78/0x90 fs/splice.c:1568
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: 0x00000002 -> 0x00000001

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 13957 Comm: syz-executor.4 Not tainted 6.7.0-rc7-syzkaller-00003-gfbafc3e621c3 #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.