CAPI: Rework application locking

Browse source

Drop the application rw-lock in favour of RCU. This synchronizes
capi20_release against capi_ctr_handle_message which may dereference an
application from (soft-)IRQ context. Any other access to the application
list is now protected by the capi_controller_lock as well. This also
allows to safely inspect applications for /proc dumping by holding
capi_controller_lock.

At this chance, drop some useless release_in_progress checks where we
obtained the application pointer from the list (which becomes NULL on
release_in_progress).

Signed-off-by: Jan Kiszka <jan.kiszka@web.de>
Signed-off-by: David S. Miller <davem@davemloft.net>

...

This commit is contained in:

Jan Kiszka 2010-02-08 10:12:15 +00:00 • committed by David S. Miller

parent 0ca3a017a7

commit 88c896ef87

2 changed files with 29 additions and 34 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

54

drivers/isdn/capi/kcapi.c

View file

11

drivers/isdn/capi/kcapi_proc.c

View file