diff options
author | nikolay@redhat.com <nikolay@redhat.com> | 2013-04-22 08:12:22 +0000 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2013-04-25 04:03:21 -0400 |
commit | c6cdcf6d82bc8f53e64ad59464e0114fe48e28bb (patch) | |
tree | 3a15cd4d3dcbb1d057d7e60fe1efb1346c0ef942 /net/vmw_vsock | |
parent | ecf01c22be034690b621d92c9ff488d607a9995a (diff) | |
download | op-kernel-dev-c6cdcf6d82bc8f53e64ad59464e0114fe48e28bb.zip op-kernel-dev-c6cdcf6d82bc8f53e64ad59464e0114fe48e28bb.tar.gz |
bonding: fix locking in enslave failure path
In commit 3c5913b53fefc9d9e15a2d0f93042766658d9f3f ("bonding:
primary_slave & curr_active_slave are not cleaned on enslave failure")
I didn't account for the use of curr_active_slave without curr_slave_lock
and since there are such users, we should hold bond->lock for writing while
setting it to NULL (in the NULL case we don't need the curr_slave_lock).
Keeping the bond lock as to avoid the extra release/acquire cycle.
Signed-off-by: Nikolay Aleksandrov <nikolay@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/vmw_vsock')
0 files changed, 0 insertions, 0 deletions