diff options
| author | Alexander Duyck <alexander.h.duyck@redhat.com> | 2014-12-31 10:56:24 -0800 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2014-12-31 18:25:54 -0500 |
| commit | 345e9b54268ae065520a7252c182d22ef4591718 (patch) | |
| tree | ad4e6c4138028f1ad00d6a2aeeb7fff90f094801 /kernel/power | |
| parent | 98293e8d2f51976d5f790400859a517c0f7cb598 (diff) | |
| download | linux-stable-345e9b54268ae065520a7252c182d22ef4591718.tar.gz linux-stable-345e9b54268ae065520a7252c182d22ef4591718.tar.bz2 linux-stable-345e9b54268ae065520a7252c182d22ef4591718.zip | |
fib_trie: Push rcu_read_lock/unlock to callers
This change is to start cleaning up some of the rcu_read_lock/unlock
handling. I realized while reviewing the code there are several spots that
I don't believe are being handled correctly or are masking warnings by
locally calling rcu_read_lock/unlock instead of calling them at the correct
level.
A common example is a call to fib_get_table followed by fib_table_lookup.
The rcu_read_lock/unlock ought to wrap both but there are several spots where
they were not wrapped.
Signed-off-by: Alexander Duyck <alexander.h.duyck@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'kernel/power')
0 files changed, 0 insertions, 0 deletions