syzbot


KCSAN: data-race in p9_client_cb / p9_client_rpc (9)

Status: auto-obsoleted due to no activity on 2022/10/12 13:20
Subsystems: v9fs
[Documentation on labels]
First crash: 531d, last: 531d
Similar bugs (8)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in p9_client_cb / p9_client_rpc (3) v9fs 2 1067d 1099d 0/26 auto-closed as invalid on 2021/04/24 11:05
upstream KCSAN: data-race in p9_client_cb / p9_client_rpc (8) v9fs 1 566d 566d 0/26 auto-closed as invalid on 2022/09/07 10:12
upstream KCSAN: data-race in p9_client_cb / p9_client_rpc (4) v9fs 5 998d 1010d 0/26 auto-closed as invalid on 2021/07/02 20:41
upstream KCSAN: data-race in p9_client_cb / p9_client_rpc (6) v9fs 1 873d 873d 0/26 auto-closed as invalid on 2021/11/04 05:57
upstream KCSAN: data-race in p9_client_cb / p9_client_rpc (5) v9fs 1 962d 962d 0/26 auto-closed as invalid on 2021/08/07 12:54
upstream KCSAN: data-race in p9_client_cb / p9_client_rpc (2) v9fs 1 1316d 1316d 0/26 auto-closed as invalid on 2020/08/17 23:12
upstream KCSAN: data-race in p9_client_cb / p9_client_rpc v9fs 2 1561d 1562d 0/26 auto-closed as invalid on 2020/01/21 10:36
upstream KCSAN: data-race in p9_client_cb / p9_client_rpc (7) v9fs 2 688d 719d 0/26 auto-closed as invalid on 2022/05/08 15:40

Sample crash report:
==================================================================
BUG: KCSAN: data-race in p9_client_cb / p9_client_rpc

write to 0xffff888136b6d5d8 of 4 bytes by task 77 on cpu 0:
 p9_client_cb+0x19/0x40 net/9p/client.c:423
 p9_conn_cancel+0x3a1/0x400 net/9p/trans_fd.c:213
 p9_poll_mux net/9p/trans_fd.c:627 [inline]
 p9_poll_workfn+0x14c/0x410 net/9p/trans_fd.c:1147
 process_one_work+0x3d3/0x720 kernel/workqueue.c:2289
 worker_thread+0x618/0xa70 kernel/workqueue.c:2436
 kthread+0x1a9/0x1e0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30

read to 0xffff888136b6d5d8 of 4 bytes by task 5258 on cpu 1:
 p9_client_rpc+0x399/0x660 net/9p/client.c:684
 p9_client_version+0xa4/0x310
 p9_client_create+0x61b/0x7a0 net/9p/client.c:985
 v9fs_session_init+0x100/0xcf0 fs/9p/v9fs.c:408
 v9fs_mount+0x78/0x660 fs/9p/vfs_super.c:126
 legacy_get_tree+0x70/0xc0 fs/fs_context.c:610
 vfs_get_tree+0x49/0x190 fs/super.c:1530
 do_new_mount+0x200/0x650 fs/namespace.c:3040
 path_mount+0x4ad/0xbb0 fs/namespace.c:3370
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount+0x281/0x2d0 fs/namespace.c:3568
 __x64_sys_mount+0x63/0x70 fs/namespace.c:3568
 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+0x63/0xcd

value changed: 0x00000002 -> 0x00000005

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 5258 Comm: syz-executor.2 Not tainted 6.0.0-rc4-syzkaller-00062-g0066f1b0e275-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
==================================================================

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/09/07 13:16 upstream 0066f1b0e275 c5b7bc57 .config console log report info [disk image] [vmlinux] ci2-upstream-kcsan-gce KCSAN: data-race in p9_client_cb / p9_client_rpc
* Struck through repros no longer work on HEAD.