Driving Safety Forward: Lessons Learned From Deploying OSS in Real-world Automotive
summary
EMQ ships an end-to-end open-source vehicle data loop that runs in mass production for ~10,000 customers, using MB-fuzzer and SP-fuzzer to find stateful MQTT broker bugs and an actor-replay system to reproduce and fix data races in one day. Architecture adds QoS prioritization, auto-buffering and cancel timeouts; tracing across ECU-to-cloud surfaces surfaces a FD-exhaustion bug (diagnostic Android client causing infinite reconnects) that breaks STR and zombifies processes, which is fixed by connection and resource limits.
AI-written summary · about
chapters (10)
- 0:00Open source in automotive
- 1:24Speaker introduction
- 3:59Data loop in software-defined vehicles
- 7:33Community safety and security
- 11:53Debugging with actor model
- 17:10Automotive OSS deployment challenges
- 21:09End-to-end open source stack
- 24:04Debugging STR in production
- 29:54Conclusion
- 30:36Q&A on ISO 26262
related talks
35mOpen Sesame! Why Functional Safety is the Master Key to Open the Door for Linux into Automotive
41mPanel: Tackling Automotive Hardware Vulnerabilities
29mAPI-fying the Engine: Replacing Legacy Automotive Protocols with REST and OAuth.
43mSecuring Software-Defined Vehicles: From Threat Awareness To Holistic Cybersecur...
14mStateful Behavior Inference and Runtime Enforcement for Vehicle Network Security
19mSecuring the future of mobility: Automotive threat modeling
37mAutomatic Automotive Hacking
50mUsing FOSS to Protect Embedded Systems Data in Transit