Project

General

Profile

Feature #3193

118: Correct use of reader-writer spinlocks

Added by Ilya Shchepetkov over 6 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Start date:
07/12/2012
Due date:
% Done:

100%

Estimated time:
Published in build:

Description

A reader-writer lock is a spinlock, except you lock it in one of two modes: a `read lock' or a `write lock'. More than one people can share a `read lock', but the write lock is exclusive: if someone has a write lock, no one can have any lock.

  • - multiple write locks are not permitted
    - multiple write unlocks are not permitted
  • - read lock is not permitted after write lock
  • - read unlock is not permitted before read lock
    - write unlock is not permitted before write lock
  • - read and write locks must be free at the end

History

#1 Updated by Ilya Shchepetkov over 6 years ago

  • % Done changed from 0 to 40

#2 Updated by Ilya Shchepetkov over 6 years ago

  • Status changed from New to Open

#3 Updated by Ilya Shchepetkov over 6 years ago

  • Status changed from Open to Resolved
  • % Done changed from 40 to 100

#4 Updated by Evgeny Novikov over 6 years ago

  • Status changed from Resolved to Open

Make a reference to commits and branches where this rule model is implemented and then mark it as resolved.

#5 Updated by Ilya Shchepetkov over 6 years ago

  • Status changed from Open to Resolved

Fixed in commit b74928f of 118_1a branch and will be merged to master together with it.

#6 Updated by Alexey Khoroshilov over 5 years ago

  • Status changed from Resolved to Open

There 3 false positives of 13 in 3.13-rc1 that can be handled by rerouter.
It makes sense to implement it.

#7 Updated by Evgeny Novikov about 5 years ago

Please, update current status.

#8 Updated by Ilya Shchepetkov about 5 years ago

Rerouter version of this model was implemented in rule118-tmpl branch.

The above three false positives are gone.

#9 Updated by Evgeny Novikov over 4 years ago

  • Status changed from Open to Closed

There are 10 false alarms for all kernel modules, 9 is due to seq_operations.

Also available in: Atom PDF