syzbot


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

Status: auto-closed as invalid on 2022/04/01 19:16
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 283d, last: 280d
similar bugs (7):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in pipe_lock / pipe_release (5) 1 354d 354d 0/24 auto-closed as invalid on 2022/01/18 04:35
upstream KCSAN: data-race in pipe_lock / pipe_release (8) 1 102d 102d 0/24 auto-closed as invalid on 2022/09/27 07:59
upstream KCSAN: data-race in pipe_lock / pipe_release (4) 1 615d 615d 0/24 auto-closed as invalid on 2021/05/02 03:19
upstream KCSAN: data-race in pipe_lock / pipe_release 2 880d 897d 0/24 auto-closed as invalid on 2020/08/09 18:16
upstream KCSAN: data-race in pipe_lock / pipe_release (3) 1 772d 772d 0/24 auto-closed as invalid on 2020/11/25 12:55
upstream KCSAN: data-race in pipe_lock / pipe_release (7) 2 212d 240d 0/24 auto-closed as invalid on 2022/06/08 19:34
upstream KCSAN: data-race in pipe_lock / pipe_release (2) 1 823d 823d 0/24 auto-closed as invalid on 2020/10/06 00:08

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

write to 0xffff888122585aec of 4 bytes by task 14901 on cpu 1:
 put_pipe_info fs/pipe.c:703 [inline]
 pipe_release+0x186/0x1e0 fs/pipe.c:733
 __fput+0x295/0x520 fs/file_table.c:317
 ____fput+0x11/0x20 fs/file_table.c:350
 task_work_run+0x8e/0x110 kernel/task_work.c:164
 tracehook_notify_resume include/linux/tracehook.h:188 [inline]
 exit_to_user_mode_loop kernel/entry/common.c:175 [inline]
 exit_to_user_mode_prepare+0x160/0x190 kernel/entry/common.c:207
 __syscall_exit_to_user_mode_work kernel/entry/common.c:289 [inline]
 syscall_exit_to_user_mode+0x20/0x40 kernel/entry/common.c:300
 do_syscall_64+0x50/0xd0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff888122585aec of 4 bytes by task 14902 on cpu 0:
 pipe_lock_nested fs/pipe.c:81 [inline]
 pipe_lock+0x13/0x40 fs/pipe.c:90
 splice_file_to_pipe+0x2a/0x360 fs/splice.c:1015
 do_splice+0xc53/0xde0 fs/splice.c:1104
 __do_splice fs/splice.c:1144 [inline]
 __do_sys_splice fs/splice.c:1350 [inline]
 __se_sys_splice+0x2bd/0x3a0 fs/splice.c:1332
 __x64_sys_splice+0x74/0x80 fs/splice.c:1332
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae

value changed: 0x00000002 -> 0x00000001

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 14902 Comm: syz-executor.1 Not tainted 5.17.0-rc5-syzkaller-00189-g53ab78cd6d5a-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================

Crashes (2):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci2-upstream-kcsan-gce 2022/02/25 19:15 upstream 53ab78cd6d5a 45a13a73 .config log report info KCSAN: data-race in pipe_lock / pipe_release
ci2-upstream-kcsan-gce 2022/02/23 01:30 upstream 917bbdb107f8 6e821dbf .config log report info KCSAN: data-race in pipe_lock / pipe_release
* Struck through repros no longer work on HEAD.