syzbot


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

Status: auto-closed as invalid on 2022/06/08 19:34
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 243d, last: 215d
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 357d 357d 0/24 auto-closed as invalid on 2022/01/18 04:35
upstream KCSAN: data-race in pipe_lock / pipe_release (8) 1 105d 105d 0/24 auto-closed as invalid on 2022/09/27 07:59
upstream KCSAN: data-race in pipe_lock / pipe_release (4) 1 618d 618d 0/24 auto-closed as invalid on 2021/05/02 03:19
upstream KCSAN: data-race in pipe_lock / pipe_release (6) 2 283d 286d 0/24 auto-closed as invalid on 2022/04/01 19:16
upstream KCSAN: data-race in pipe_lock / pipe_release 2 883d 900d 0/24 auto-closed as invalid on 2020/08/09 18:16
upstream KCSAN: data-race in pipe_lock / pipe_release (3) 1 776d 776d 0/24 auto-closed as invalid on 2020/11/25 12:55
upstream KCSAN: data-race in pipe_lock / pipe_release (2) 1 826d 826d 0/24 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 0xffff888104982a2c of 4 bytes by task 3792 on cpu 1:
 put_pipe_info fs/pipe.c:704 [inline]
 pipe_release+0x164/0x1c0 fs/pipe.c:734
 __fput+0x292/0x510 fs/file_table.c:317
 ____fput+0x11/0x20 fs/file_table.c:350
 task_work_run+0x8e/0x110 kernel/task_work.c:164
 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
 exit_to_user_mode_loop+0x124/0x130 kernel/entry/common.c:169
 exit_to_user_mode_prepare kernel/entry/common.c:201 [inline]
 __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]
 syscall_exit_to_user_mode+0x6a/0x90 kernel/entry/common.c:294
 do_syscall_64+0x37/0x70 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x44/0xae

read to 0xffff888104982a2c of 4 bytes by task 3793 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+0xc05/0xd90 fs/splice.c:1104
 __do_splice fs/splice.c:1144 [inline]
 __do_sys_splice fs/splice.c:1350 [inline]
 __se_sys_splice+0x2a4/0x380 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+0x2b/0x70 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: 3793 Comm: syz-executor.3 Not tainted 5.18.0-rc5-syzkaller-00028-ga7391ad35724-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/05/04 19:29 upstream a7391ad35724 dc9e5259 .config log report info KCSAN: data-race in pipe_lock / pipe_release
ci2-upstream-kcsan-gce 2022/04/06 15:48 upstream 3e732ebf7316 97582466 .config log report info KCSAN: data-race in pipe_lock / pipe_release
* Struck through repros no longer work on HEAD.