From: Andy Gospodarek <andy@greyhouse.net>
To: Krzysztof Oledzki <olel@ans.pl>
Cc: Jay Vosburgh <fubar@us.ibm.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
bugme-daemon@bugzilla.kernel.org,
shemminger@linux-foundation.org, davem@davemloft.net,
netdev@vger.kernel.org, andy@greyhouse.net
Subject: Re: [Bugme-new] [Bug 9543] New: RTNL: assertion failed at net/ipv6/addrconf.c (2164)/RTNL: assertion failed at net/ipv4/devinet.c (1055)
Date: Fri, 14 Dec 2007 13:26:38 -0500 [thread overview]
Message-ID: <20071214182638.GC25879@gospo.usersys.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0712141707090.30334@bizon.gios.gov.pl>
On Fri, Dec 14, 2007 at 05:14:57PM +0100, Krzysztof Oledzki wrote:
>
>
> On Wed, 12 Dec 2007, Jay Vosburgh wrote:
>
> >Herbert Xu <herbert@gondor.apana.org.au> wrote:
> >
> >>>diff -puN drivers/net/bonding/bond_sysfs.c~bonding-locking-fix
> >>>drivers/net/bonding/bond_sysfs.c
> >>>--- a/drivers/net/bonding/bond_sysfs.c~bonding-locking-fix
> >>>+++ a/drivers/net/bonding/bond_sysfs.c
> >>>@@ -1111,8 +1111,6 @@ static ssize_t bonding_store_primary(str
> >>>out:
> >>> write_unlock_bh(&bond->lock);
> >>>
> >>>- rtnl_unlock();
> >>>-
> >>
> >>Looking at the changeset that added this perhaps the intention
> >>is to hold the lock? If so we should add an rtnl_lock to the start
> >>of the function.
> >
> > Yes, this function needs to hold locks, and more than just
> >what's there now. I believe the following should be correct; I haven't
> >tested it, though (I'm supposedly on vacation right now).
> >
> > The following change should be correct for the
> >bonding_store_primary case discussed in this thread, and also corrects
> >the bonding_store_active case which performs similar functions.
> >
> > The bond_change_active_slave and bond_select_active_slave
> >functions both require rtnl, bond->lock for read and curr_slave_lock for
> >write_bh, and no other locks. This is so that the lower level
> >mode-specific functions can release locks down to just rtnl in order to
> >call, e.g., dev_set_mac_address with the locks it expects (rtnl only).
> >
> >Signed-off-by: Jay Vosburgh <fubar@us.ibm.com>
> >
> >diff --git a/drivers/net/bonding/bond_sysfs.c
> >b/drivers/net/bonding/bond_sysfs.c
> >index 11b76b3..28a2d80 100644
> >--- a/drivers/net/bonding/bond_sysfs.c
> >+++ b/drivers/net/bonding/bond_sysfs.c
> >@@ -1075,7 +1075,10 @@ static ssize_t bonding_store_primary(struct device
> >*d,
> > struct slave *slave;
> > struct bonding *bond = to_bond(d);
> >
> >- write_lock_bh(&bond->lock);
> >+ rtnl_lock();
> >+ read_lock(&bond->lock);
> >+ write_lock_bh(&bond->curr_slave_lock);
> >+
> > if (!USES_PRIMARY(bond->params.mode)) {
> > printk(KERN_INFO DRV_NAME
> > ": %s: Unable to set primary slave; %s is in mode
> > %d\n",
> >@@ -1109,8 +1112,8 @@ static ssize_t bonding_store_primary(struct device
> >*d,
> > }
> > }
> >out:
> >- write_unlock_bh(&bond->lock);
> >-
> >+ write_unlock_bh(&bond->curr_slave_lock);
> >+ read_unlock(&bond->lock);
> > rtnl_unlock();
> >
> > return count;
> >@@ -1190,7 +1193,8 @@ static ssize_t bonding_store_active_slave(struct
> >device *d,
> > struct bonding *bond = to_bond(d);
> >
> > rtnl_lock();
> >- write_lock_bh(&bond->lock);
> >+ read_lock(&bond->lock);
> >+ write_lock_bh(&bond->curr_slave_lock);
> >
> > if (!USES_PRIMARY(bond->params.mode)) {
> > printk(KERN_INFO DRV_NAME
> >@@ -1247,7 +1251,8 @@ static ssize_t bonding_store_active_slave(struct
> >device *d,
> > }
> > }
> >out:
> >- write_unlock_bh(&bond->lock);
> >+ write_unlock_bh(&bond->curr_slave_lock);
> >+ read_unlock(&bond->lock);
> > rtnl_unlock();
> >
> > return count;
>
> Vanilla 2.6.24-rc5 plus this patch:
>
> =========================================================
> [ INFO: possible irq lock inversion dependency detected ]
> 2.6.24-rc5 #1
> ---------------------------------------------------------
> events/0/9 just changed the state of lock:
> (&mc->mca_lock){-+..}, at: [<c0411c7a>] mld_ifc_timer_expire+0x130/0x1fb
> but this lock took another, soft-read-irq-unsafe lock in the past:
> (&bond->lock){-.--}
>
> and interrupts could create inverse lock ordering between them.
>
>
Grrr, I should have seen that -- sorry. Try your luck with this instead:
diff --git a/drivers/net/bonding/bond_sysfs.c b/drivers/net/bonding/bond_sysfs.c
index 11b76b3..0694254 100644
--- a/drivers/net/bonding/bond_sysfs.c
+++ b/drivers/net/bonding/bond_sysfs.c
@@ -1075,7 +1075,10 @@ static ssize_t bonding_store_primary(struct device *d,
struct slave *slave;
struct bonding *bond = to_bond(d);
- write_lock_bh(&bond->lock);
+ rtnl_lock();
+ read_lock_bh(&bond->lock);
+ write_lock_bh(&bond->curr_slave_lock);
+
if (!USES_PRIMARY(bond->params.mode)) {
printk(KERN_INFO DRV_NAME
": %s: Unable to set primary slave; %s is in mode %d\n",
@@ -1109,8 +1112,8 @@ static ssize_t bonding_store_primary(struct device *d,
}
}
out:
- write_unlock_bh(&bond->lock);
-
+ write_unlock_bh(&bond->curr_slave_lock);
+ read_unlock_bh(&bond->lock);
rtnl_unlock();
return count;
@@ -1190,7 +1193,8 @@ static ssize_t bonding_store_active_slave(struct device *d,
struct bonding *bond = to_bond(d);
rtnl_lock();
- write_lock_bh(&bond->lock);
+ read_lock_bh(&bond->lock);
+ write_lock_bh(&bond->curr_slave_lock);
if (!USES_PRIMARY(bond->params.mode)) {
printk(KERN_INFO DRV_NAME
@@ -1247,7 +1251,8 @@ static ssize_t bonding_store_active_slave(struct device *d,
}
}
out:
- write_unlock_bh(&bond->lock);
+ write_unlock_bh(&bond->curr_slave_lock);
+ read_unlock_bh(&bond->lock);
rtnl_unlock();
return count;
next prev parent reply other threads:[~2007-12-14 18:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9543-10286@http.bugzilla.kernel.org/>
2007-12-11 11:46 ` [Bugme-new] [Bug 9543] New: RTNL: assertion failed at net/ipv6/addrconf.c (2164)/RTNL: assertion failed at net/ipv4/devinet.c (1055) Andrew Morton
2007-12-11 15:04 ` Krzysztof Oledzki
2007-12-11 20:30 ` Andrew Morton
2007-12-12 13:31 ` Herbert Xu
2007-12-12 17:46 ` Jay Vosburgh
2007-12-12 19:07 ` Andy Gospodarek
2007-12-14 16:14 ` Krzysztof Oledzki
2007-12-14 18:26 ` Andy Gospodarek [this message]
2007-12-14 18:57 ` Krzysztof Oledzki
2007-12-14 22:03 ` Andy Gospodarek
2007-12-14 22:11 ` Krzysztof Oledzki
2007-12-14 22:27 ` Andy Gospodarek
2007-12-18 19:52 ` Krzysztof Oledzki
2007-12-14 22:47 ` Andy Gospodarek
2007-12-15 4:10 ` Herbert Xu
2007-12-15 15:09 ` Andy Gospodarek
2007-12-16 2:27 ` Herbert Xu
2007-12-16 3:17 ` Andy Gospodarek
2007-12-16 3:23 ` Herbert Xu
2007-12-18 19:53 ` Krzysztof Oledzki
2007-12-19 14:42 ` Andy Gospodarek
2008-01-07 17:57 ` Krzysztof Oledzki
2008-01-07 20:26 ` Andy Gospodarek
2008-01-07 20:40 ` Jay Vosburgh
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=20071214182638.GC25879@gospo.usersys.redhat.com \
--to=andy@greyhouse.net \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=olel@ans.pl \
--cc=shemminger@linux-foundation.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).