syzbot


KCSAN: data-race in pipe_release / pipe_wait_writable (5)

Status: moderation: reported on 2026/04/06 20:47
Subsystems: fs
[Documentation on labels]
Reported-by: syzbot+c81efef83e6c9bd13559@syzkaller.appspotmail.com
First crash: 4d12h, last: 4d12h
✨ AI Jobs (1)
ID Workflow Result Correct Bug Created Started Finished Revision Error
015e9f11-d079-44ea-b110-1fb7d562a77f assessment-kcsan Benign: ✅  Confident: ✅  KCSAN: data-race in pipe_release / pipe_wait_writable (5) 2026/04/06 20:46 2026/04/06 20:46 2026/04/06 21:07 4440e7c2e964875f9e35dba6deda12c2195f19d3
Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in pipe_release / pipe_wait_writable fs 6 1 1543d 1543d 0/29 auto-closed as invalid on 2022/02/23 01:29
upstream KCSAN: data-race in pipe_release / pipe_wait_writable (2) fs 6 1 1248d 1248d 0/29 auto-obsoleted due to no activity on 2022/12/15 02:24
upstream KCSAN: data-race in pipe_release / pipe_wait_writable (4) fs 6 2 168d 189d 0/29 auto-obsoleted due to no activity on 2025/12/19 13:50
upstream KCSAN: data-race in pipe_release / pipe_wait_writable (3) fs 6 2 254d 254d 0/29 auto-obsoleted due to no activity on 2025/09/25 08:20

Sample crash report:
==================================================================
BUG: KCSAN: data-race in pipe_release / pipe_wait_writable

read-write to 0xffff88811bdfb5ac of 4 bytes by task 9866 on cpu 1:
 put_pipe_info fs/pipe.c:714 [inline]
 pipe_release+0x16a/0x1d0 fs/pipe.c:744
 __fput+0x29b/0x650 fs/file_table.c:469
 fput_close_sync+0xad/0x190 fs/file_table.c:574
 __do_sys_close fs/open.c:1509 [inline]
 __se_sys_close fs/open.c:1494 [inline]
 __x64_sys_close+0x55/0xf0 fs/open.c:1494
 x64_sys_call+0x275d/0x3020 arch/x86/include/generated/asm/syscalls_64.h:4
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x12c/0x370 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff88811bdfb5ac of 4 bytes by task 9863 on cpu 0:
 pipe_lock fs/pipe.c:90 [inline]
 pipe_wait_writable+0x202/0x250 fs/pipe.c:1084
 wait_for_space fs/splice.c:1272 [inline]
 vmsplice_to_pipe fs/splice.c:1551 [inline]
 __do_sys_vmsplice fs/splice.c:1608 [inline]
 __se_sys_vmsplice+0x42b/0xfd0 fs/splice.c:1578
 __x64_sys_vmsplice+0x55/0x70 fs/splice.c:1578
 x64_sys_call+0x28e9/0x3020 arch/x86/include/generated/asm/syscalls_64.h:279
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x12c/0x370 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x00000002 -> 0x00000001

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 9863 Comm: syz.1.2745 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
==================================================================

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/04/06 20:46 upstream bfe62a454542 4440e7c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in pipe_release / pipe_wait_writable
* Struck through repros no longer work on HEAD.