[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071215041052.GA25324@gondor.apana.org.au>
Date: Sat, 15 Dec 2007 12:10:52 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Andy Gospodarek <andy@...yhouse.net>
Cc: Krzysztof Oledzki <olel@....pl>, Jay Vosburgh <fubar@...ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
bugme-daemon@...zilla.kernel.org, shemminger@...ux-foundation.org,
davem@...emloft.net, netdev@...r.kernel.org
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)
On Fri, Dec 14, 2007 at 05:47:22PM -0500, Andy Gospodarek wrote:
>
> I'm guessing if we go back to using a write-lock for bond->lock this
> will go back to working again, but I'm not totally convinced since there
> are plenty of places where we used a read-lock with it.
Sorry I forgot to cc you earlier Andy.
But to fix this you need make sure that all read locks on bond->lock
in process context disable BH. This is because at least one write
lock can be taken from BH context.
You don't need to turn the read locks into write locks however.
This is also something that we can undo once the set_multicast
interface has been fixed to not take the tx lock.
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists