ELCE11: Sandboxing for automotive Linux [LWN.net]

ELCE11: Sandboxing for automotive Linux

Posted Nov 3, 2011 1:26 UTC (Thu) by Cyberax (✭ supporter ✭, #52523)
Parent article: ELCE11: Sandboxing for automotive Linux

Could they post the models of cars which are going to run in-car entertainment and navigation/lighting controls on the same CPU? I need to know which models I should avoid.

to post comments

ELCE11: Sandboxing for automotive Linux

Posted Nov 3, 2011 7:23 UTC (Thu) by simlo (guest, #10866) [Link] (2 responses)

If you have real-time operating system - with no bugs - it should not be a problem. Of course, any OS have a bug somewhere - especially around ensuring timing.

I once saw Windriver talking about the same thing: Using time slices for virtual machines (running VxWorks) within a simplified VxWorks. This was for aerospace, not automotive.

ELCE11: Sandboxing for automotive Linux

Posted Nov 3, 2011 16:23 UTC (Thu) by Cyberax (✭ supporter ✭, #52523) [Link]

I don't trust OS-level sandboxes to contain malicious processes. System-level sandboxes (KVM, Xen) just might be able to do it but even that is doubtful.

That's why I'd just separate critical functionality into a completely separate CPU, maybe even with a separate network.

ELCE11: Sandboxing for automotive Linux

Posted Nov 10, 2011 20:17 UTC (Thu) by lamadiHH (guest, #80884) [Link]

When you refer to "aerospace" I think you mean VxWorks 653 that is compliant to the ARINC 653 (Integrated Modular Avionics). This edition is qualified according to DAL A and thus meets the highest safety requirements in the industry. VxWorks is not Linux.