From: Stephen Hemminger <shemminger@osdl.org>
To: Brian Braunstein <brian@bristyle.com>
Cc: netdev@vger.kernel.org, rajesh_mish@yahoo.com
Subject: Re: PATCH: br_stp.c:271: ignoring BPDUs if cost goes up
Date: Wed, 30 Aug 2006 12:11:36 -0700 [thread overview]
Message-ID: <20060830121136.0e96246e@localhost.localdomain> (raw)
In-Reply-To: <44F5D334.7050205@bristyle.com>
On Wed, 30 Aug 2006 11:04:36 -0700
Brian Braunstein <brian@bristyle.com> wrote:
> PATCH
> problem at: br_stp.c:271
> problem: ignoring BPDUs if cost goes up
>
> i was refered to email these addresses by the bridging code author.
>
> please see the full problem description and patch at:
> http://mesh.calit2.net/calmesh/one/linux_kernel_modifications/bridge_ignoring_bpdus/
>
> if you would like to have it attached or inline with the email instead
> let me know.
>
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
That code has been around a long time and probably came from pseudo-code in earlier
version of the 802.1d standard. The current version of the standard has
switched to RSTP and now has unreadable railroad track state machine
diagrams, rather than pseudo-code. So it is hard to check if your fix
is correct or not.
--
Stephen Hemminger <shemminger@osdl.org>
next prev parent reply other threads:[~2006-08-30 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 18:04 PATCH: br_stp.c:271: ignoring BPDUs if cost goes up Brian Braunstein
2006-08-30 19:02 ` Stephen Hemminger
2006-08-30 19:11 ` Stephen Hemminger [this message]
2006-08-30 21:24 ` Stephen Hemminger
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=20060830121136.0e96246e@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=brian@bristyle.com \
--cc=netdev@vger.kernel.org \
--cc=rajesh_mish@yahoo.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 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.