From: Alex Zeffertt <ajz@cambridgebroadband.com>
To: bridge@lists.osdl.org
Subject: [Bridge] bridge_list orphans in linux-2.4
Date: Thu, 21 Sep 2006 14:42:22 +0100 [thread overview]
Message-ID: <451296BE.1060002@cambridgebroadband.com> (raw)
Hi all,
We use linux-2.4.20 in one of our products and we've found what looks
to be a problem in the bridge module. (I know this is old code but we
don't send our customers kernel upgrades unless we really have to!)
The problem is that some of our bridges have become orphaned from the
bridge module. Specifically
ifconfig ourbridgename
shows that the device "ourbridgename" is known to the kernel, but
brctl show
does not list "ourbridgename".
I've looked through the bridge module and it seems that the most likely
explanation is that bridge_list in br_if.c has become corrupted, causing
the bridge called "ourbridgename" to become orphaned.
I cannot see how this would happen, however, since bridge_list is only
ever referenced under the ioctl_mutex. I should also point out that
br_del_bridge() is not called by our application.
I noticed that in later kernels the ioctl_mutex has been replaced by
the rtnl_lock(). Why was this done? Could this be related to our
problem?
TIA,
Alex
next reply other threads:[~2006-09-21 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 13:42 Alex Zeffertt [this message]
2006-09-21 22:56 ` [Bridge] bridge_list orphans in linux-2.4 Stephen Hemminger
[not found] <AA48EE0D609E8547912F0039B5E47BC261BE14@SHI-EXCHBE1.shipara.hcltech.com>
2006-12-15 15:01 ` Alex Zeffertt
2006-12-15 18:24 ` Stephen Hemminger
2006-12-15 18:31 ` Stephen Hemminger
2006-12-18 10:01 ` Alex Zeffertt
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=451296BE.1060002@cambridgebroadband.com \
--to=ajz@cambridgebroadband.com \
--cc=bridge@lists.osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.