Considering Linux for functional safety relevant system architecture: Pitfalls and Potential

Developing safety-critical software components incurs significantly higher costs compared to non-safety ones, urging an emphasis on minimizing their number and complexity, as per safety standards. While GNU/Linux offers a rich set of features, its original design lacks a safety-centric focus. Ensuring safety in Linux-based systems poses challenges due to the kernel's diverse interaction capabilities, requiring meticulous attention to safety requirements. Addressing safety starts with defining the technology device's intended function, encompassing user experience and essential services like device maintenance. Functional safety extends beyond individual components, necessitating systemwide consideration, even for “safety elements out of context.” Integrating safetyrelated and non-safety software demands careful design to prevent adverse impacts on safety modules. Proposed solutions must address functional safety, cybersecurity, and long-term maintenance obligations, essential for compliance with regulations. This talk explores architectural considerations and necessary precautions for leveraging GNU/Linux in safety applications, facilitating robust software systems that meet stringent safety standards.