From: Shmulik Hen <shmulik.hen@intel.com>
To: "Ned Bass" <bass6@llnl.gov>, <bonding-devel@lists.sourceforge.net>
Cc: netdev@oss.sgi.com
Subject: Re: [Bonding-devel] [BUG] kernel panic on ifconfig bond0 down
Date: Thu, 18 Sep 2003 12:42:58 +0300 [thread overview]
Message-ID: <200309181242.58258.shmulik.hen@intel.com> (raw)
In-Reply-To: <E791C176A6139242A988ABA8B3D9B38A02A464D8@hasmsx403.iil.intel.com>
On Wednesday 17 September 2003 11:44 pm, Ned Bass wrote:
> Note that the key to make the panic happen is step #3, bringing up
> the slave interface. I realize that the slave interface is not
> supposed to be brought up prior to bringing up the bonding
> interface, but should probably not cause a kernel panic either :).
> The panic occurs immediately after entering 'ifconfig bond0 down'.
> Also, the panic does not occur if I only enslave eth0 but not eth1.
>
>
There was a bug in patch 8 of the cleanup set that left a dangling
pointer in bond_release_all(). Definitely may bad for not announcing
that (and removing the patch set from SFG ?). I was relying on the
fact that people won't test it after I announced the set needs to be
re-done after finding a potential bug in patch 5.
I'm currently in the final stages of re-creating the set after
implementing the bug fixes and doing some improvements resulting from
internal code reviews. Perhaps this time I should publish it as an
"experimental" patch set and give everyone a chance to try it out
while our QA group grinds it to dust.
--
| Shmulik Hen Advanced Network Services |
| Israel Design Center, Jerusalem |
| LAN Access Division, Platform Networking |
| Intel Communications Group, Intel corp. |
next parent reply other threads:[~2003-09-18 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E791C176A6139242A988ABA8B3D9B38A02A464D8@hasmsx403.iil.intel.com>
2003-09-18 9:42 ` Shmulik Hen [this message]
2003-09-18 16:40 ` [Bonding-devel] [BUG] kernel panic on ifconfig bond0 down 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=200309181242.58258.shmulik.hen@intel.com \
--to=shmulik.hen@intel.com \
--cc=bass6@llnl.gov \
--cc=bonding-devel@lists.sourceforge.net \
--cc=netdev@oss.sgi.com \
/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).