diff options
author | Pavel Emelyanov <xemul@openvz.org> | 2008-05-07 19:44:20 +0400 |
---|---|---|
committer | John W. Linville <linville@tuxdriver.com> | 2008-05-21 21:47:42 -0400 |
commit | 5194ee82b4aafc35b32c96db11bdacea9bf548be (patch) | |
tree | f8d774ace25060590bf73763ba62be46822f65e0 /net/tipc/port.c | |
parent | 402d7752ed253369b7ab037e2d778e52d59c19ed (diff) | |
download | blackbird-op-linux-5194ee82b4aafc35b32c96db11bdacea9bf548be.tar.gz blackbird-op-linux-5194ee82b4aafc35b32c96db11bdacea9bf548be.zip |
mac80211: Fix one more call to synchronize_rcu in atomic context.
(This set applies OK without the previous one of 4 patches,
but with some fuzz in the 7th one)
The mesh_path_node_free() does so under hashwlock.
But, this one is called
1. from mesh_path_add() after an old hash is hidden and
synchronize_rcu() is calld
2. mesh_pathtbl_unregister(), when the module is being
unloaded and no devices exist to mess with this hash.
So, it seems to me, that simply removing the call is OK.
Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'net/tipc/port.c')
0 files changed, 0 insertions, 0 deletions