https://forge.ispras.ru/https://forge.ispras.ru/favicon.ico?16490126692012-07-12T09:18:39ZOpen-Source ProjectsLinux Kernel Safety RuleDB - Feature #3193: 118: Correct use of reader-writer spinlockshttps://forge.ispras.ru/issues/3193?journal_id=118182012-07-12T09:18:39ZIlya Shchepetkovshchepetkov@ispras.ru
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>40</i></li></ul> Linux Kernel Safety RuleDB - Feature #3193: 118: Correct use of reader-writer spinlockshttps://forge.ispras.ru/issues/3193?journal_id=118282012-07-12T10:35:20ZIlya Shchepetkovshchepetkov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Open</i></li></ul> Linux Kernel Safety RuleDB - Feature #3193: 118: Correct use of reader-writer spinlockshttps://forge.ispras.ru/issues/3193?journal_id=119732012-07-17T11:28:32ZIlya Shchepetkovshchepetkov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>40</i> to <i>100</i></li></ul> Linux Kernel Safety RuleDB - Feature #3193: 118: Correct use of reader-writer spinlockshttps://forge.ispras.ru/issues/3193?journal_id=120012012-07-18T06:42:02ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Open</i></li></ul><p>Make a reference to commits and branches where this rule model is implemented and then mark it as resolved.</p> Linux Kernel Safety RuleDB - Feature #3193: 118: Correct use of reader-writer spinlockshttps://forge.ispras.ru/issues/3193?journal_id=120042012-07-18T08:34:55ZIlya Shchepetkovshchepetkov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Resolved</i></li></ul><p>Fixed in commit b74928f of 118_1a branch and will be merged to master together with it.</p> Linux Kernel Safety RuleDB - Feature #3193: 118: Correct use of reader-writer spinlockshttps://forge.ispras.ru/issues/3193?journal_id=183832013-12-09T19:59:24ZAlexey Khoroshilovkhoroshilov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Open</i></li></ul><p>There 3 false positives of 13 in 3.13-rc1 that can be handled by rerouter.<br />It makes sense to implement it.</p> Linux Kernel Safety RuleDB - Feature #3193: 118: Correct use of reader-writer spinlockshttps://forge.ispras.ru/issues/3193?journal_id=186412014-02-22T06:05:03ZEvgeny Novikovnovikov@ispras.ru
<ul></ul><p>Please, update current status.</p> Linux Kernel Safety RuleDB - Feature #3193: 118: Correct use of reader-writer spinlockshttps://forge.ispras.ru/issues/3193?journal_id=186752014-03-05T13:54:54ZIlya Shchepetkovshchepetkov@ispras.ru
<ul></ul><p>Rerouter version of this model was implemented in rule118-tmpl branch.</p>
<p>The above three false positives are gone.</p> Linux Kernel Safety RuleDB - Feature #3193: 118: Correct use of reader-writer spinlockshttps://forge.ispras.ru/issues/3193?journal_id=209432014-10-21T13:20:07ZEvgeny Novikovnovikov@ispras.ru
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>There are 10 false alarms for all kernel modules, 9 is due to seq_operations.</p>