diff options
author | Nick Piggin <npiggin@suse.de> | 2010-04-01 04:09:40 -0400 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2010-04-05 22:50:02 -0400 |
commit | 5fbfb18d7a5b846946d52c4a10e3aaa213ec31b6 (patch) | |
tree | bcfa13dec8cb2527c3007b3e5f957cb50e571c64 /firmware/ti_3410.fw.ihex | |
parent | 7da23b86e14b77c094b11a9fa5ef5b3758fc9193 (diff) |
Fix up possibly racy module refcounting
Module refcounting is implemented with a per-cpu counter for speed.
However there is a race when tallying the counter where a reference may
be taken by one CPU and released by another. Reference count summation
may then see the decrement without having seen the previous increment,
leading to lower than expected count. A module which never has its
actual reference drop below 1 may return a reference count of 0 due to
this race.
Module removal generally runs under stop_machine, which prevents this
race causing bugs due to removal of in-use modules. However there are
other real bugs in module.c code and driver code (module_refcount is
exported) where the callers do not run under stop_machine.
Fix this by maintaining running per-cpu counters for the number of
module refcount increments and the number of refcount decrements. The
increments are tallied after the decrements, so any decrement seen will
always have its corresponding increment counted. The final refcount is
the difference of the total increments and decrements, preventing a
low-refcount from being returned.
Signed-off-by: Nick Piggin <npiggin@suse.de>
Acked-by: Rusty Russell <rusty@rustcorp.com.au>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'firmware/ti_3410.fw.ihex')
0 files changed, 0 insertions, 0 deletions