[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6186.1256953523@death.nxdomain.ibm.com>
Date: Fri, 30 Oct 2009 18:45:23 -0700
From: Jay Vosburgh <fubar@...ibm.com>
To: ebiederm@...ssion.com (Eric W. Biederman)
cc: David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [PATCH 0/6] Bonding simplifications and netns support
Eric W. Biederman <ebiederm@...ssion.com> wrote:
>Jay Vosburgh <fubar@...ibm.com> writes:
>
>> No, to both questions. Also, if I back out the 7 bonding
>> patches, the same insmod / rmmod does not panic.
>>
>> I just set it up and did it again. Fresh boot of the system
>> (which doesn't load bonding); "insmod drivers/net/bonding/bonding.ko;
>> rmmod bonding" and blammo.
>>
>> A little bisect action reveals that the problem first appears
>> after applying the fifth patch (below). Does a basic insmod / rmmod
>> cycle work ok for you? I'm specifying no options to bonding.
>
>It works here. The only issue I found was that veth wasn't quite
>working. I am wondering if there was some version of the tree
>where rtnl_link_unregister is broken and you applied the patches to that.
Must have been, I did a pull of net-next-2.6 and it seems to
work ok now. Not sure what it was; I was only a day or so behind.
Anyway, it doesn't panic now; I'll give it some further testing next
week.
-J
---
-Jay Vosburgh, IBM Linux Technology Center, fubar@...ibm.com
--
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