[moderation] [fs?] KCSAN: data-race in pipe_release / wait_for_partner (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 021533194476 Kconfig: Disable -Wstringop-overflow for GCC ..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1219cb97e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=b75adb52627a8379
dashboard link: https://syzkaller.appspot.com/bug?extid=ad79ac1cfe402399a64b
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/b2f6a21a62ff/disk-02153319.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/90e0e75c7922/vmlinux-02153319.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4dfed5f7a347/bzImage-02153319.xz

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

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

read-write to 0xffff88812e0a196c of 4 bytes by task 5906 on cpu 1:
put_pipe_info fs/pipe.c:722 [inline]
pipe_release+0x164/0x1c0 fs/pipe.c:752
__fput+0x299/0x630 fs/file_table.c:376
__fput_sync+0x44/0x50 fs/file_table.c:461
__do_sys_close fs/open.c:1554 [inline]
__se_sys_close+0xfa/0x1a0 fs/open.c:1539
__x64_sys_close+0x1f/0x30 fs/open.c:1539
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

read to 0xffff88812e0a196c of 4 bytes by task 5899 on cpu 0:
pipe_lock_nested fs/pipe.c:81 [inline]
pipe_lock fs/pipe.c:90 [inline]
wait_for_partner+0x105/0x1d0 fs/pipe.c:1102
fifo_open+0x483/0x5e0 fs/pipe.c:1169
do_dentry_open+0x637/0xbd0 fs/open.c:953
vfs_open+0x4a/0x50 fs/open.c:1087
do_open fs/namei.c:3641 [inline]
path_openat+0x1821/0x1d40 fs/namei.c:3798
do_filp_open+0xf6/0x200 fs/namei.c:3825
do_sys_openat2+0xab/0x110 fs/open.c:1404
do_sys_open fs/open.c:1419 [inline]
__do_sys_open fs/open.c:1427 [inline]
__se_sys_open fs/open.c:1423 [inline]
__x64_sys_open+0xe6/0x110 fs/open.c:1423
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x1d0 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: 5899 Comm: syz-executor.0 Not tainted 6.8.0-rc2-syzkaller-00199-g021533194476 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/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.