syzbot


KCSAN: data-race in p9_conn_cancel / p9_write_work (5)

Status: moderation: reported on 2024/04/07 07:31
Subsystems: v9fs
[Documentation on labels]
Reported-by: syzbot+ea89179830fc4c224e62@syzkaller.appspotmail.com
First crash: 29d, last: 4d14h
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in p9_conn_cancel / p9_write_work (4) v9fs 2 160d 184d 0/26 auto-obsoleted due to no activity on 2024/01/02 07:46
upstream KCSAN: data-race in p9_conn_cancel / p9_write_work v9fs 1 1258d 1242d 0/26 auto-closed as invalid on 2020/12/30 07:04
upstream KCSAN: data-race in p9_conn_cancel / p9_write_work (3) v9fs 1 748d 748d 0/26 auto-closed as invalid on 2022/05/24 19:24
upstream KCSAN: data-race in p9_conn_cancel / p9_write_work (2) v9fs 2 1190d 1202d 0/26 auto-closed as invalid on 2021/03/08 14:39

Sample crash report:
==================================================================
BUG: KCSAN: data-race in p9_conn_cancel / p9_write_work

write to 0xffff8881177f8828 of 4 bytes by task 3523 on cpu 1:
 p9_conn_cancel+0x89/0x400 net/9p/trans_fd.c:199
 p9_poll_mux net/9p/trans_fd.c:631 [inline]
 p9_poll_workfn+0x133/0x420 net/9p/trans_fd.c:1177
 process_one_work kernel/workqueue.c:3267 [inline]
 process_scheduled_works+0x465/0x990 kernel/workqueue.c:3348
 worker_thread+0x526/0x730 kernel/workqueue.c:3429
 kthread+0x1d1/0x210 kernel/kthread.c:388
 ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

read to 0xffff8881177f8828 of 4 bytes by task 3176 on cpu 0:
 p9_write_work+0x26/0x750 net/9p/trans_fd.c:453
 process_one_work kernel/workqueue.c:3267 [inline]
 process_scheduled_works+0x465/0x990 kernel/workqueue.c:3348
 worker_thread+0x526/0x730 kernel/workqueue.c:3429
 kthread+0x1d1/0x210 kernel/kthread.c:388
 ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

value changed: 0x00000000 -> 0xffffff98

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 3176 Comm: kworker/0:4 Not tainted 6.9.0-rc6-syzkaller-00053-g0106679839f7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: events p9_write_work
==================================================================
bridge0: port 2(bridge_slave_1) entered blocking state
bridge0: port 2(bridge_slave_1) entered forwarding state
bridge0: port 1(bridge_slave_0) entered blocking state
bridge0: port 1(bridge_slave_0) entered forwarding state

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/05/02 06:50 upstream 0106679839f7 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in p9_conn_cancel / p9_write_work
2024/04/07 07:30 upstream f2f80ac80987 ca620dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in p9_conn_cancel / p9_write_work
* Struck through repros no longer work on HEAD.