From: Jeff Golds <jgolds@resilience.com>
To: linux-kernel@vger.kernel.org
Subject: Panic after using bonding driver
Date: Thu, 29 Mar 2001 09:41:18 -0800 [thread overview]
Message-ID: <3AC373BE.FCE96825@resilience.com> (raw)
I have been working on a driver similar to the bonding driver and have
come across a bug in the bonding driver code. When the bonding driver
enslaves a device, it modifies the slave's multicast list to be the
master's multicast list. Later, after the master is downed, the kernel
gets a panic if you try to down the slave device.
To get around this problem, there are two solutions that I see:
1) Don't do multicasting for bonding devices
While this works (I've tested) some peple might call this a serious
limitation.
2) Keep track of the slave's multicast list
This would require keeping a copy of the slave's pointer and restoring
it when the bonding
device is downed. Not sure if this would even work since the slave's
multicast list might
be stale by the time it is restored.
I'd like to get this fixed in the best possible way. What are your
folks comments in regard to the matter?
-Jeff
--
Jeff Golds
jgolds@resilience.com
reply other threads:[~2001-03-29 17:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3AC373BE.FCE96825@resilience.com \
--to=jgolds@resilience.com \
--cc=linux-kernel@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