syzbot


KCSAN: data-race in p9_conn_cancel / p9_poll_workfn (9)

Status: upstream: reported on 2025/02/07 13:31
Subsystems: v9fs
[Documentation on labels]
Reported-by: syzbot+483d6c9b9231ea7e1851@syzkaller.appspotmail.com
First crash: 16h37m, last: 16h37m
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [v9fs?] KCSAN: data-race in p9_conn_cancel / p9_poll_workfn (9) 0 (1) 2025/02/07 13:31
Similar bugs (8)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in p9_conn_cancel / p9_poll_workfn (4) v9fs 1 315d 315d 0/28 auto-obsoleted due to no activity on 2024/05/02 19:52
upstream KCSAN: data-race in p9_conn_cancel / p9_poll_workfn (7) v9fs 2 146d 160d 0/28 auto-obsoleted due to no activity on 2024/10/19 18:15
upstream KCSAN: data-race in p9_conn_cancel / p9_poll_workfn (2) v9fs 1 564d 564d 0/28 auto-obsoleted due to no activity on 2023/08/28 09:43
upstream KCSAN: data-race in p9_conn_cancel / p9_poll_workfn (5) v9fs 1 279d 279d 0/28 auto-obsoleted due to no activity on 2024/06/08 01:35
upstream KCSAN: data-race in p9_conn_cancel / p9_poll_workfn (6) v9fs 1 235d 235d 0/28 auto-obsoleted due to no activity on 2024/07/22 12:28
upstream KCSAN: data-race in p9_conn_cancel / p9_poll_workfn (3) v9fs 1 505d 505d 0/28 auto-obsoleted due to no activity on 2023/10/26 00:39
upstream KCSAN: data-race in p9_conn_cancel / p9_poll_workfn (8) v9fs 1 74d 74d 0/28 auto-obsoleted due to no activity on 2025/01/20 09:01
upstream KCSAN: data-race in p9_conn_cancel / p9_poll_workfn v9fs 1 1259d 1259d 0/28 auto-closed as invalid on 2021/10/01 19:17

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

write to 0xffff888164f81828 of 4 bytes by task 4264 on cpu 1:
 p9_conn_cancel+0x89/0x400 net/9p/trans_fd.c:199
 p9_write_work+0x3ac/0x750 net/9p/trans_fd.c:522
 process_one_work kernel/workqueue.c:3236 [inline]
 process_scheduled_works+0x483/0x9a0 kernel/workqueue.c:3317
 worker_thread+0x51d/0x6f0 kernel/workqueue.c:3398
 kthread+0x4ae/0x520 kernel/kthread.c:464
 ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

read to 0xffff888164f81828 of 4 bytes by task 9 on cpu 0:
 p9_poll_mux net/9p/trans_fd.c:625 [inline]
 p9_poll_workfn+0xc0/0x410 net/9p/trans_fd.c:1177
 process_one_work kernel/workqueue.c:3236 [inline]
 process_scheduled_works+0x483/0x9a0 kernel/workqueue.c:3317
 worker_thread+0x51d/0x6f0 kernel/workqueue.c:3398
 kthread+0x4ae/0x520 kernel/kthread.c:464
 ret_from_fork+0x4b/0x60 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

value changed: 0x00000000 -> 0xffffffe0

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 UID: 0 PID: 9 Comm: kworker/0:1 Not tainted 6.14.0-rc1-syzkaller-00081-gbb066fe812d6 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
Workqueue: events p9_poll_workfn
==================================================================

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/02/07 02:22 upstream bb066fe812d6 8002dd28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in p9_conn_cancel / p9_poll_workfn
* Struck through repros no longer work on HEAD.