From: Paul Smith <paul@mad-scientist.net>
To: Linux netdev <netdev@vger.kernel.org>
Subject: Re: 2.6.27.18: bnx2/tg3: BUG: "scheduling while atomic" trying to ifenslave a second interface to my bond
Date: Wed, 15 Apr 2009 01:29:27 -0400 [thread overview]
Message-ID: <1239773367.6499.170.camel@homebase.localnet> (raw)
In-Reply-To: <11276.1239757967@death.nxdomain.ibm.com>
On Tue, 2009-04-14 at 18:12 -0700, Jay Vosburgh wrote:
> I think I know what's going on. I believe this patch will
> resolve things, but I won't be able to test it until tomorrow. If you
> want to test this, great; if you want to wait, that's fine too.
I tested this; it works great. All my systems came up fine with this
change applied. Thanks!
> diff --git a/drivers/net/bonding/bond_alb.c b/drivers/net/bonding/bond_alb.c
> index 8dc6fbb..b22467a 100644
> --- a/drivers/net/bonding/bond_alb.c
> +++ b/drivers/net/bonding/bond_alb.c
> @@ -1708,10 +1708,8 @@ void bond_alb_handle_active_change(struct bonding *bond, struct slave *new_slave
> * Called with RTNL
> */
> int bond_alb_set_mac_address(struct net_device *bond_dev, void *addr)
> - __releases(&bond->curr_slave_lock)
> - __releases(&bond->lock)
> __acquires(&bond->lock)
> - __acquires(&bond->curr_slave_lock)
> + __releases(&bond->lock)
> {
> struct bonding *bond = netdev_priv(bond_dev);
> struct sockaddr *sa = addr;
> @@ -1747,9 +1745,6 @@ int bond_alb_set_mac_address(struct net_device *bond_dev, void *addr)
> }
> }
>
> - write_unlock_bh(&bond->curr_slave_lock);
> - read_unlock(&bond->lock);
> -
> if (swap_slave) {
> alb_swap_mac_addr(bond, swap_slave, bond->curr_active_slave);
> alb_fasten_mac_swap(bond, swap_slave, bond->curr_active_slave);
> @@ -1757,16 +1752,17 @@ int bond_alb_set_mac_address(struct net_device *bond_dev, void *addr)
> alb_set_slave_mac_addr(bond->curr_active_slave, bond_dev->dev_addr,
> bond->alb_info.rlb_enabled);
>
> - alb_send_learning_packets(bond->curr_active_slave, bond_dev->dev_addr);
> + read_lock(&bond->lock);
> + alb_send_learning_packets(bond->curr_active_slave,
> + bond_dev->dev_addr);
> if (bond->alb_info.rlb_enabled) {
> /* inform clients mac address has changed */
> - rlb_req_update_slave_clients(bond, bond->curr_active_slave);
> + rlb_req_update_slave_clients(bond,
> + bond->curr_active_slave);
> }
> + read_unlock(&bond->lock);
> }
>
> - read_lock(&bond->lock);
> - write_lock_bh(&bond->curr_slave_lock);
> -
> return 0;
> }
>
--
Paul Smith <paul@mad-scientist.net>
next prev parent reply other threads:[~2009-04-15 5:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 21:15 2.6.27.18: bnx2/tg3: BUG: "scheduling while atomic" trying to ifenslave a second interface to my bond Paul Smith
2009-04-14 16:01 ` Paul Smith
2009-04-14 21:29 ` Brian Haley
2009-04-15 1:12 ` Jay Vosburgh
2009-04-15 3:23 ` David Miller
2009-04-15 5:29 ` Paul Smith [this message]
2009-04-15 16:56 ` Paul Smith
2009-04-15 18:11 ` Jay Vosburgh
2009-04-15 18:39 ` Paul Smith
[not found] ` <1241397581.6499.658.camel@homebase.localnet>
2009-05-04 19:03 ` 2.6.27.18: bnx2/tg3: BUG: "scheduling while atomic" trying toifenslave " Jay Vosburgh
2009-05-04 19:06 ` David Miller
2009-05-04 22:38 ` Paul Smith
2009-05-04 22:44 ` David Miller
2009-05-05 0:59 ` Paul Smith
2009-05-04 23:00 ` 2.6.27.18: bnx2/tg3: BUG: "scheduling while atomic" tryingtoifenslave " Jay Vosburgh
2009-05-04 23:04 ` David Miller
2009-05-04 23:05 ` 2.6.27.18: bnx2/tg3: BUG: "scheduling while atomic" trying toifenslave " Ben Hutchings
2009-05-04 23:12 ` David Miller
2009-05-05 4:32 ` 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=1239773367.6499.170.camel@homebase.localnet \
--to=paul@mad-scientist.net \
--cc=netdev@vger.kernel.org \
/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).