syzbot


KCSAN: data-race in pipe_lock / pipe_release (13)

Status: auto-obsoleted due to no activity on 2024/03/25 04:35
Subsystems: fs
[Documentation on labels]
Reported-by: syzbot+e4fd2021fa9d8c3b8ac9@syzkaller.appspotmail.com
First crash: 60d, last: 60d
Similar bugs (12)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in pipe_lock / pipe_release (5) fs 1 857d 857d 0/26 auto-closed as invalid on 2022/01/18 04:35
upstream KCSAN: data-race in pipe_lock / pipe_release (8) fs 1 605d 605d 0/26 auto-closed as invalid on 2022/09/27 07:59
upstream KCSAN: data-race in pipe_lock / pipe_release (4) fs 1 1118d 1118d 0/26 auto-closed as invalid on 2021/05/02 03:19
upstream KCSAN: data-race in pipe_lock / pipe_release (11) fs 1 206d 206d 0/26 auto-obsoleted due to no activity on 2023/10/31 07:05
upstream KCSAN: data-race in pipe_lock / pipe_release (6) fs 2 783d 786d 0/26 auto-closed as invalid on 2022/04/01 19:16
upstream KCSAN: data-race in pipe_lock / pipe_release (9) fs 6 350d 480d 0/26 auto-obsoleted due to no activity on 2023/06/09 03:35
upstream KCSAN: data-race in pipe_lock / pipe_release fs 2 1383d 1400d 0/26 auto-closed as invalid on 2020/08/09 18:16
upstream KCSAN: data-race in pipe_lock / pipe_release (3) fs 1 1276d 1276d 0/26 auto-closed as invalid on 2020/11/25 12:55
upstream KCSAN: data-race in pipe_lock / pipe_release (12) fs 1 114d 114d 0/26 auto-obsoleted due to no activity on 2024/01/31 07:04
upstream KCSAN: data-race in pipe_lock / pipe_release (7) fs 2 715d 743d 0/26 auto-closed as invalid on 2022/06/08 19:34
upstream KCSAN: data-race in pipe_lock / pipe_release (10) fs 2 287d 308d 0/26 auto-obsoleted due to no activity on 2023/08/10 23:17
upstream KCSAN: data-race in pipe_lock / pipe_release (2) fs 1 1326d 1326d 0/26 auto-closed as invalid on 2020/10/06 00:08

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

read-write to 0xffff888138244eac of 4 bytes by task 25618 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 0xffff888138244eac of 4 bytes by task 25620 on cpu 0:
 pipe_lock_nested fs/pipe.c:81 [inline]
 pipe_lock+0x17/0x40 fs/pipe.c:90
 ipipe_prep fs/splice.c:1677 [inline]
 splice_pipe_to_pipe fs/splice.c:1752 [inline]
 do_splice+0x200/0x10d0 fs/splice.c:1331
 __do_splice fs/splice.c:1436 [inline]
 __do_sys_splice fs/splice.c:1652 [inline]
 __se_sys_splice+0x24c/0x380 fs/splice.c:1634
 __x64_sys_splice+0x78/0x90 fs/splice.c:1634
 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: 25620 Comm: syz-executor.1 Not tainted 6.8.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
==================================================================

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/02/19 04:34 upstream b401b621758e 578f7538 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in pipe_lock / pipe_release
* Struck through repros no longer work on HEAD.