diff options
author | David S. Miller <davem@davemloft.net> | 2012-01-24 17:03:44 -0500 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-02-03 09:19:04 -0800 |
commit | f217c4711d71aa6811b6e71d219b9efafa5d55a6 (patch) | |
tree | dff8657b88953fc3b5b930e799bb85290910157e /net/rose | |
parent | d020b1d3d3379d183d0649cdc2f6de9131268419 (diff) |
rds: Make rds_sock_lock BH rather than IRQ safe.
[ Upstream commit efc3dbc37412c027e363736b4f4c74ee5e8ecffc ]
rds_sock_info() triggers locking warnings because we try to perform a
local_bh_enable() (via sock_i_ino()) while hardware interrupts are
disabled (via taking rds_sock_lock).
There is no reason for rds_sock_lock to be a hardware IRQ disabling
lock, none of these access paths run in hardware interrupt context.
Therefore making it a BH disabling lock is safe and sufficient to
fix this bug.
Reported-by: Kumar Sanghvi <kumaras@chelsio.com>
Reported-by: Josh Boyer <jwboyer@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/rose')
0 files changed, 0 insertions, 0 deletions