Formalizing Safety Rules 2 » History » Version 1
Evgeny Novikov, 07/30/2013 10:54 AM
1 | 1 | Evgeny Novikov | h1. Formalizing Safety Rules 2 |
---|---|---|---|
2 | |||
3 | Before starting formalizing safety rules you need to create an account at this site. The name of this account should be sent to managers of the LDV project, e.g. via e-mail. Then somebody will add you to developers of the LDV project and you will be able to create and to update feature requests and bug reports "here":http://forge.ispras.ru/projects/ldv-rules/issues. |
||
4 | |||
5 | Formalizing safety rules consists of following activities that can be fully or partially repeated several times. |
||
6 | |||
7 | h2. Understanding and informal description of the rule |
||
8 | |||
9 | Just one time per each rule you need to reserve a rule identifier by creating a feature request "here":http://forge.ispras.ru/projects/ldv-rules/issues. The rule identifier is a number. This number should be greater by one then the maximum of already reserved numbers. Note that you won''t be able to change the rule identifier. |
||
10 | |||
11 | To understand the rule you need: |
||
12 | * To read available documentation of the relevant kernel core API. |
||
13 | * To explore source code of the Linux kernel. For instance, you may use http://lxr.linux.no or http://lxr.free-electrons.com. |
||
14 | * To analyze verification results that you will obtained at one of the following steps. |
||
15 | * To discuss it with developers of the LDV project. |
||
16 | |||
17 | "Here":http://linuxtesting.org/ldv/online?action=show_rule&rule_id=0032 you can find an example of a good description of a rule. |