syzbot


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

Status: auto-closed as invalid on 2022/01/18 04:35
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 358d, last: 358d
similar bugs (7):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in pipe_lock / pipe_release (8) 1 106d 106d 0/24 auto-closed as invalid on 2022/09/27 07:59
upstream KCSAN: data-race in pipe_lock / pipe_release (4) 1 619d 619d 0/24 auto-closed as invalid on 2021/05/02 03:19
upstream KCSAN: data-race in pipe_lock / pipe_release (6) 2 285d 287d 0/24 auto-closed as invalid on 2022/04/01 19:16
upstream KCSAN: data-race in pipe_lock / pipe_release 2 885d 902d 0/24 auto-closed as invalid on 2020/08/09 18:16
upstream KCSAN: data-race in pipe_lock / pipe_release (3) 1 777d 777d 0/24 auto-closed as invalid on 2020/11/25 12:55
upstream KCSAN: data-race in pipe_lock / pipe_release (7) 2 217d 245d 0/24 auto-closed as invalid on 2022/06/08 19:34
upstream KCSAN: data-race in pipe_lock / pipe_release (2) 1 827d 827d 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 0xffff888136eb436c of 4 bytes by task 27904 on cpu 0:
 put_pipe_info fs/pipe.c:702 [inline]
 pipe_release+0x186/0x1e0 fs/pipe.c:732
 __fput+0x295/0x520 fs/file_table.c:280
 ____fput+0x11/0x20 fs/file_table.c:313
 task_work_run+0x8e/0x110 kernel/task_work.c:164
 tracehook_notify_resume include/linux/tracehook.h:189 [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 0xffff888136eb436c of 4 bytes by task 27932 on cpu 1:
 pipe_lock_nested fs/pipe.c:80 [inline]
 pipe_lock+0x13/0x40 fs/pipe.c:89
 splice_from_pipe fs/splice.c:596 [inline]
 generic_splice_sendpage+0x82/0xd0 fs/splice.c:746
 do_splice_from fs/splice.c:767 [inline]
 do_splice+0xa0e/0xde0 fs/splice.c:1079
 __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: 1 PID: 27932 Comm: syz-executor.0 Not tainted 5.16.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================

Crashes (1):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci2-upstream-kcsan-gce 2021/12/14 04:28 upstream 5472f14a3742 5d14b1ea .config log report info KCSAN: data-race in pipe_lock / pipe_release
* Struck through repros no longer work on HEAD.