From: Jay Vosburgh <fubar@us.ibm.com>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH 0/6] Bonding simplifications and netns support
Date: Fri, 30 Oct 2009 18:45:23 -0700 [thread overview]
Message-ID: <6186.1256953523@death.nxdomain.ibm.com> (raw)
In-Reply-To: <m1ljisid8n.fsf@fess.ebiederm.org>
Eric W. Biederman <ebiederm@xmission.com> wrote:
>Jay Vosburgh <fubar@us.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@us.ibm.com
next prev parent reply other threads:[~2009-10-31 1:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 0:16 [PATCH 0/6] Bonding simplifications and netns support Eric W. Biederman
2009-10-30 0:18 ` [PATCH 1/6] net: Allow devices to specify a device specific sysfs group Eric W. Biederman
2009-10-30 0:18 ` [PATCH 2/6] bond: Simply bond sysfs group creation Eric W. Biederman
2009-10-30 0:18 ` [PATCH 3/6] bond: Simplify bond_create Eric W. Biederman
2009-10-30 0:18 ` [PATCH 4/6] bond: Simplify bond device destruction Eric W. Biederman
2009-10-30 0:18 ` [PATCH 5/6] bond: Implement a basic set of rtnl link ops Eric W. Biederman
2009-10-30 8:06 ` Patrick McHardy
2009-10-30 8:29 ` Patrick McHardy
2009-10-30 9:23 ` Eric W. Biederman
2009-10-30 9:33 ` Patrick McHardy
2009-10-30 9:58 ` [PATCH 7/6] bond: Get the rtnl_link_ops support correct Eric W. Biederman
2009-10-30 10:00 ` [PATCH 5/6] bond: Implement a basic set of rtnl link ops Eric W. Biederman
2009-10-30 10:08 ` Patrick McHardy
2009-10-30 0:18 ` [PATCH 6/6] bond: Add support for multiple network namespaces Eric W. Biederman
2009-10-30 6:25 ` [PATCH 0/6] Bonding simplifications and netns support David Miller
2009-10-30 6:38 ` Eric Dumazet
2009-10-30 6:40 ` David Miller
2009-10-30 7:50 ` Eric W. Biederman
2009-10-30 10:39 ` Eric W. Biederman
2009-10-30 19:41 ` David Miller
2009-10-30 21:12 ` Jay Vosburgh
2009-10-30 22:57 ` Eric W. Biederman
2009-10-31 0:10 ` Jay Vosburgh
2009-10-31 1:06 ` Eric W. Biederman
2009-10-31 1:45 ` Jay Vosburgh [this message]
2009-10-31 0:27 ` Eric W. Biederman
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=6186.1256953523@death.nxdomain.ibm.com \
--to=fubar@us.ibm.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--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).