syzbot

 sign-in | mailing list | source | docs
🐞 Open [991] ≡ Subsystems 🐞 Fixed [5244] 🐞 Invalid [12523] ⬇ Missing Backports [83] 📈 Kernel Health 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes 💬 Send us feedback

KCSAN: data-race in can_receive / can_stat_update (7)

Status: auto-obsoleted due to no activity on 2023/05/15 22:30
Subsystems: can
[Documentation on labels]
First crash: 402d, last: 382d
▶ ▼ Similar bugs (7)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KCSAN: data-race in can_receive / can_stat_update (4) can 2 648d 662d 0/26 auto-closed as invalid on 2022/08/22 20:20
upstream KCSAN: data-race in can_receive / can_stat_update (2) can 1 1124d 1124d 0/26 auto-closed as invalid on 2021/05/04 12:50
upstream KCSAN: data-race in can_receive / can_stat_update (3) can 5 703d 776d 0/26 auto-closed as invalid on 2022/06/29 13:32
upstream KCSAN: data-race in can_receive / can_stat_update can 3 1549d 1572d 0/26 auto-closed as invalid on 2020/04/09 06:18
upstream KCSAN: data-race in can_receive / can_stat_update (6) can 1 453d 453d 0/26 auto-obsoleted due to no activity on 2023/03/13 11:08
upstream KCSAN: data-race in can_receive / can_stat_update (8) can 2 331d 345d 0/26 auto-obsoleted due to no activity on 2023/07/05 18:24
upstream KCSAN: data-race in can_receive / can_stat_update (5) can 1 604d 604d 0/26 auto-closed as invalid on 2022/10/06 14:19

Sample crash report:
==================================================================
BUG: KCSAN: data-race in can_receive / can_stat_update

read-write to 0xffff888120e10268 of 8 bytes by interrupt on cpu 1:
 can_receive+0x62/0x1f0 net/can/af_can.c:650
 canfd_rcv+0xe7/0x180 net/can/af_can.c:702
 __netif_receive_skb_one_core net/core/dev.c:5479 [inline]
 __netif_receive_skb+0x90/0x1b0 net/core/dev.c:5593
 process_backlog+0x21f/0x380 net/core/dev.c:5921
 __napi_poll+0x60/0x3b0 net/core/dev.c:6482
 napi_poll net/core/dev.c:6549 [inline]
 net_rx_action+0x31a/0x6c0 net/core/dev.c:6659
 __do_softirq+0xc1/0x265 kernel/softirq.c:571
 run_ksoftirqd+0x17/0x20 kernel/softirq.c:934
 smpboot_thread_fn+0x30a/0x4a0 kernel/smpboot.c:164
 kthread+0x1a6/0x1e0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308

read to 0xffff888120e10268 of 8 bytes by interrupt on cpu 0:
 can_stat_update+0x444/0x6b0 net/can/proc.c:152
 call_timer_fn+0x35/0x290 kernel/time/timer.c:1700
 expire_timers kernel/time/timer.c:1751 [inline]
 __run_timers+0x46c/0x650 kernel/time/timer.c:2022
 run_timer_softirq+0x1d/0x40 kernel/time/timer.c:2035
 __do_softirq+0xc1/0x265 kernel/softirq.c:571
 run_ksoftirqd+0x17/0x20 kernel/softirq.c:934
 smpboot_thread_fn+0x30a/0x4a0 kernel/smpboot.c:164
 kthread+0x1a6/0x1e0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308

value changed: 0x0000000000001065 -> 0x0000000000001066

Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 12 Comm: ksoftirqd/0 Not tainted 6.3.0-rc6-syzkaller-00016-g0d3eb744aed4 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
==================================================================
GRED: Unable to relocate VQ 0x0 after dequeue, screwing up backlog
GRED: Unable to relocate VQ 0x0 after dequeue, screwing up backlog
GRED: Unable to relocate VQ 0x0 after dequeue, screwing up backlog
GRED: Unable to relocate VQ 0x0 after dequeue, screwing up backlog
GRED: Unable to relocate VQ 0x0 after dequeue, screwing up backlog

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/04/10 22:25 upstream 0d3eb744aed4 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-kcsan-gce KCSAN: data-race in can_receive / can_stat_update
2023/03/22 16:49 upstream a1effab7a3a3 f94b4a29 .config console log report info ci2-upstream-kcsan-gce KCSAN: data-race in can_receive / can_stat_update
* Struck through repros no longer work on HEAD.