Refining the Linux kernel CAN stack for RHIVOS
summary
Plan to add drop-reason on SKB tracepoints and a new CAN socket diag module so ss can list CAN sockets and why frames are dropped; drop-reason patches are in review and the diag module is about to be sent to netdev. Upstream Kselftests for vcan+hardware land the tests into kernel CI, letting virtual CAN tests run in VMs and reuse the same tests on real devices. UAPI moves to rtnetlink YAML UAPI so iproute2/YAML tooling can set bitrate and keep stable enums without rebuilding userland.
AI-written summary · about
chapters (5)
- 0:00RHIVOS and CAN stack goals
- 3:17CAN stack observability and debug
- 6:52CAN stack K self tests
- 9:42CAN stack config and docs
- 12:11Q&A and upstream readiness
related talks
36mLinux Kernel Developer Panel
03mIntroduction
27mTuning in-kernel routines on RISC-V
39mCAN Bus in Control, Automotive and Satellites
18mSolving Pre-silicon Kernel Upstream for RISC-V First Ever
27mPlugging into the Red Hat kernel CI ecosystem
42mProtecting the Linux Kernel from Confidential Computing Threats in Virtual Environments
19mUpstream kernel CI using patchew and TDC