Project

General

Profile

Feature #3399

143: Usage of semaphores

Added by Vladimir Gratinskiy about 7 years ago. Updated about 5 years ago.

Status:
Open
Priority:
Normal
Start date:
09/04/2012
Due date:
% Done:

100%

Estimated time:
Published in build:

Description

It is necessary to use semaphore correctly. This rule checks usage of the functions: up_read, down_read, up_write, down_write, down_read_trylock, down_write_trylock, downgrade_write, down_read_nested, down_write_nested.

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

Commit 82163edcdf on torvalds fix the last one.

Links
Sample bugfixes 506218e, de79143

History

#1

Updated by Vladimir Gratinskiy about 7 years ago

  • Description updated (diff)
#2

Updated by Vladimir Gratinskiy about 7 years ago

  • Description updated (diff)
#3

Updated by Vadim Mutilin about 7 years ago

More commits from linux-stable
de79143
506218e

#4

Updated by Vladimir Gratinskiy over 6 years ago

  • Description updated (diff)
  • % Done changed from 0 to 100

New tests showed that write lock in read section is not permitted.

#5

Updated by Vadim Mutilin about 5 years ago

  • Description updated (diff)

Also available in: Atom PDF