From: Nikolay Aleksandrov <nikolay@redhat.com>
To: netdev@vger.kernel.org
Cc: hariprasad@chelsio.com, vfalico@gmail.com, j.vosburgh@gmail.com,
andy@greyhouse.net, davem@davemloft.net,
Nikolay Aleksandrov <nikolay@redhat.com>
Subject: [PATCH net-next v2 3/7] bonding: alb: clean bond->lock
Date: Tue, 9 Sep 2014 23:16:59 +0200 [thread overview]
Message-ID: <1410297423-26624-4-git-send-email-nikolay@redhat.com> (raw)
In-Reply-To: <1410297423-26624-1-git-send-email-nikolay@redhat.com>
We can remove the lock/unlock as it's no longer necessary since
RTNL should be held while calling bond_alb_set_mac_address().
Signed-off-by: Nikolay Aleksandrov <nikolay@redhat.com>
---
drivers/net/bonding/bond_alb.c | 11 ++---------
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git a/drivers/net/bonding/bond_alb.c b/drivers/net/bonding/bond_alb.c
index 73c21e233131..028496205f39 100644
--- a/drivers/net/bonding/bond_alb.c
+++ b/drivers/net/bonding/bond_alb.c
@@ -1775,8 +1775,7 @@ void bond_alb_handle_link_change(struct bonding *bond, struct slave *slave, char
* Set the bond->curr_active_slave to @new_slave and handle
* mac address swapping and promiscuity changes as needed.
*
- * If new_slave is NULL, caller must hold curr_slave_lock or
- * bond->lock for write.
+ * If new_slave is NULL, caller must hold curr_slave_lock for write
*
* If new_slave is not NULL, caller must hold RTNL, curr_slave_lock
* for write. Processing here may sleep, so no other locks may be held.
@@ -1857,12 +1856,8 @@ void bond_alb_handle_active_change(struct bonding *bond, struct slave *new_slave
write_lock_bh(&bond->curr_slave_lock);
}
-/*
- * Called with RTNL
- */
+/* Called with RTNL */
int bond_alb_set_mac_address(struct net_device *bond_dev, void *addr)
- __acquires(&bond->lock)
- __releases(&bond->lock)
{
struct bonding *bond = netdev_priv(bond_dev);
struct sockaddr *sa = addr;
@@ -1895,14 +1890,12 @@ int bond_alb_set_mac_address(struct net_device *bond_dev, void *addr)
} else {
alb_set_slave_mac_addr(curr_active, bond_dev->dev_addr);
- read_lock(&bond->lock);
alb_send_learning_packets(curr_active,
bond_dev->dev_addr, false);
if (bond->alb_info.rlb_enabled) {
/* inform clients mac address has changed */
rlb_req_update_slave_clients(bond, curr_active);
}
- read_unlock(&bond->lock);
}
return 0;
--
1.9.3
next prev parent reply other threads:[~2014-09-09 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 21:16 [PATCH net-next v2 0/7] bonding: get rid of bond->lock Nikolay Aleksandrov
2014-09-09 21:16 ` [PATCH net-next v2 1/7] cxgb4: remove bond->lock Nikolay Aleksandrov
2014-09-09 21:16 ` [PATCH net-next v2 2/7] bonding: 3ad: use curr_slave_lock instead of bond->lock Nikolay Aleksandrov
2014-09-09 21:16 ` Nikolay Aleksandrov [this message]
2014-09-09 21:17 ` [PATCH net-next v2 4/7] bonding: convert primary_slave to use RCU Nikolay Aleksandrov
2014-09-09 21:17 ` [PATCH net-next v2 5/7] bonding: procfs: clean bond->lock usage and " Nikolay Aleksandrov
2014-09-09 21:17 ` [PATCH net-next v2 6/7] bonding: options: remove bond->lock usage Nikolay Aleksandrov
2014-09-09 21:17 ` [PATCH net-next v2 7/7] bonding: remove last users of bond->lock and bond->lock itself Nikolay Aleksandrov
2014-09-10 0:32 ` [PATCH net-next v2 0/7] bonding: get rid of bond->lock David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1410297423-26624-4-git-send-email-nikolay@redhat.com \
--to=nikolay@redhat.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=hariprasad@chelsio.com \
--cc=j.vosburgh@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vfalico@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).