syzbot


KCSAN: data-race in pipe_double_lock / pipe_release (7)

Status: moderation: reported on 2025/02/21 13:48
Subsystems: fs
[Documentation on labels]
Reported-by: syzbot+71c1e30992fb93a8774d@syzkaller.appspotmail.com
First crash: 17h15m, last: 17h15m
Similar bugs (6)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in pipe_double_lock / pipe_release (3) fs 1 494d 494d 0/28 auto-obsoleted due to no activity on 2023/11/21 02:37
upstream KCSAN: data-race in pipe_double_lock / pipe_release (4) fs 1 401d 401d 0/28 auto-obsoleted due to no activity on 2024/02/21 21:32
upstream KCSAN: data-race in pipe_double_lock / pipe_release (5) fs 1 255d 255d 0/28 auto-obsoleted due to no activity on 2024/07/16 19:28
upstream KCSAN: data-race in pipe_double_lock / pipe_release (2) fs 1 599d 599d 0/28 auto-obsoleted due to no activity on 2023/08/07 23:55
upstream KCSAN: data-race in pipe_double_lock / pipe_release fs 1 1709d 1709d 0/28 auto-closed as invalid on 2020/07/23 17:42
upstream KCSAN: data-race in pipe_double_lock / pipe_release (6) fs 1 107d 107d 0/28 auto-obsoleted due to no activity on 2025/01/01 13:02

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

read-write to 0xffff88812627842c of 4 bytes by task 5187 on cpu 0:
 put_pipe_info fs/pipe.c:713 [inline]
 pipe_release+0x15e/0x1c0 fs/pipe.c:743
 __fput+0x2ac/0x640 fs/file_table.c:464
 ____fput+0x1c/0x30 fs/file_table.c:492
 task_work_run+0x13a/0x1a0 kernel/task_work.c:227
 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
 exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
 exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]
 __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
 syscall_exit_to_user_mode+0xa8/0x120 kernel/entry/common.c:218
 do_syscall_64+0xd6/0x1c0 arch/x86/entry/common.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff88812627842c of 4 bytes by task 5188 on cpu 1:
 pipe_lock fs/pipe.c:91 [inline]
 pipe_double_lock+0x2e/0xa0 fs/pipe.c:111
 link_pipe fs/splice.c:1873 [inline]
 do_tee+0x2e9/0x940 fs/splice.c:1976
 __do_sys_tee fs/splice.c:2004 [inline]
 __se_sys_tee+0x93/0x130 fs/splice.c:1988
 __x64_sys_tee+0x55/0x70 fs/splice.c:1988
 x64_sys_call+0x2269/0x2dc0 arch/x86/include/generated/asm/syscalls_64.h:277
 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: 1 UID: 0 PID: 5188 Comm: syz.7.22960 Not tainted 6.14.0-rc3-syzkaller-00166-g334426094588 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
==================================================================

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/02/21 13:47 upstream 334426094588 0808a665 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in pipe_double_lock / pipe_release
* Struck through repros no longer work on HEAD.