gsoc:2019-gsoc-safety-critical-linux
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
gsoc:2019-gsoc-safety-critical-linux [2019/01/24 12:12] lukas.bulwahn |
gsoc:2019-gsoc-safety-critical-linux [2019/03/04 12:53] (current) lukas.bulwahn start to edit titles to be closer to ELISA |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Linux in High-Integrity Regulated Environments ====== | + | ====== GSoC Projects around Enabling Linux in Safety Applications (ELISA) ====== |
| [[:gsoc:google-summer-code-2019|Main GSoC Linux Foundation page: How to apply, deadlines, other workgroups, ...]] | [[:gsoc:google-summer-code-2019|Main GSoC Linux Foundation page: How to apply, deadlines, other workgroups, ...]] | ||
| - | To use Linux in High-Integrity Regulated Environment, such as safety-critical systems, security systems or systems subject to other regulatory norms, it requires to show evidences that Linux has a high software quality. | + | To use Linux in high-integrity regulated environment, such as safety-critical systems, security systems or systems subject to other regulatory norms, it requires to show evidences that Linux has a high software quality. High software quality is roughly assessed by two classes of measurements: |
| - | High software quality is roughly assessed by two classes of measurements: | + | |
| * Observation, Measurement and Assessment of the Software Development Process and Practices | * Observation, Measurement and Assessment of the Software Development Process and Practices | ||
| Line 11: | Line 10: | ||
| The Google Summer of Code Projects are activities that contribute to those two fields of work. | The Google Summer of Code Projects are activities that contribute to those two fields of work. | ||
| - | Primary mentoring contacts: Lukas Bulwahn, lukas.bulwahn at gmail.com, Julia Lawall julia.lawall at lip6.fr, Nicholas Mc Guire, der.herr at hofr.at, Ralf Ramsauer | + | Primary mentoring contacts: Lukas Bulwahn, lukas.bulwahn at gmail.com; Julia Lawall, julia.lawall at lip6.fr; Nicholas Mc Guire, der.herr at hofr.at; Ralf Ramsauer, ralf.ramsauer at oth-regensburg.de |
| - | ==== Some background on previous activities in safety-critical systems ==== | + | ==== Some background on Enabling Linux in Safety Applications ==== |
| The SIL2LinuxMP project is an collaborative research project to provide procedures and methods to qualify Linux on a multi-core embedded platform at safety integrity level 2 (SIL2) according to IEC 61508 Ed 2. | The SIL2LinuxMP project is an collaborative research project to provide procedures and methods to qualify Linux on a multi-core embedded platform at safety integrity level 2 (SIL2) according to IEC 61508 Ed 2. | ||
| Line 24: | Line 23: | ||
| https://www.youtube.com/watch?v=1eyJ6dAqMmg | https://www.youtube.com/watch?v=1eyJ6dAqMmg | ||
| + | |||
| The SIL2LinuxMP project has ended at the end of 2018 and the activities around Linux in safety-critical systems will be continued in a new organisational structure in 2019. | The SIL2LinuxMP project has ended at the end of 2018 and the activities around Linux in safety-critical systems will be continued in a new organisational structure in 2019. | ||
| Line 29: | Line 29: | ||
| ====== Student Project Proposals 2019 ====== | ====== Student Project Proposals 2019 ====== | ||
| - | ==== Applying Clang Thread Sanitizer to Linux Kernel ==== | + | ==== Applying Clang Thread Safety Analyser to Linux Kernel ==== |
| - | The Linux kernel can be compiled with clang recently. This allows to employ clang tools to the Linux kernel source. The clang thread sanitizer is a tool to detect when data is accessed without being locked before, when suitable annotations are provided. The GSoC student project proposal should describe how you would use the clang thread sanitizer to detect missing locks for on widely used and central kernel data structures in the Linux kernel. The GSoC student project proposal should sketch how this would implemented, it would be best to provide an example and foreseen challenges and explain which the first investigations and design decisions need to be done and provide a first working assumption on those design decisions. | + | The Linux kernel can be compiled with clang recently. This allows to employ clang tools to the Linux kernel source. The clang thread safety analyser is a tool to detect when data is accessed without being locked before, when suitable annotations are provided. The GSoC student project proposal should describe how you would use the clang thread safety Analyser to detect missing locks for on widely used and central kernel data structures in the Linux kernel. The GSoC student project proposal should sketch how this would implemented, it would be best to provide an example and foreseen challenges and explain which the first investigations and design decisions need to be done and provide a first working assumption on those design decisions. |
| Main contact person for this project proposal: Lukas Bulwahn, lukas.bulwahn at gmail.com | Main contact person for this project proposal: Lukas Bulwahn, lukas.bulwahn at gmail.com | ||
| Line 47: | Line 47: | ||
| The issue tracker, https://github.com/lfd/PaStA/issues, provides a good overview of possible student activities in a GSoC project related to PaStA. A student start look into those issues and determine a suitable selection of tasks and goals from that issue tracker that can be handled within the timeframe of the GSoC project. A project proposal should breakdown the goals stated in the issue tracker to a more detailed plan of activities, needed extensions of PaStA and the implementation tasks. | The issue tracker, https://github.com/lfd/PaStA/issues, provides a good overview of possible student activities in a GSoC project related to PaStA. A student start look into those issues and determine a suitable selection of tasks and goals from that issue tracker that can be handled within the timeframe of the GSoC project. A project proposal should breakdown the goals stated in the issue tracker to a more detailed plan of activities, needed extensions of PaStA and the implementation tasks. | ||
| - | Main contact person for this project proposal: Ralf Ramsauer | + | Main contact person for this project proposal: Ralf Ramsauer, ralf.ramsauer at oth-regensburg.de |
| ==== Handling Complex Types and Attributes in Coccinelle ==== | ==== Handling Complex Types and Attributes in Coccinelle ==== | ||
| Line 57: | Line 57: | ||
| This project is relevant to Linux, Zephyr and many more applications. | This project is relevant to Linux, Zephyr and many more applications. | ||
| - | Main contact person for this project proposal: Julia Lawall <julia.lawall@lip6.fr> | + | Main contact person for this project proposal: Julia Lawall, julia.lawall at lip6.fr |
| ==== Develop Methods for Tracking Tool Analysis Findings over Time ==== | ==== Develop Methods for Tracking Tool Analysis Findings over Time ==== | ||
gsoc/2019-gsoc-safety-critical-linux.1548331946.txt.gz · Last modified: 2019/01/24 12:12 by lukas.bulwahn
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
