resubmit bridge: fix message_age_timer calculation
Subsystems (3)
PATCH 1/1 resubmit bridge: fix message_age_timer calculation
This changes the message_age_timer calculation to use the BPDU's max age as opposed to the local bridge's max age. This is in accordance with section 8.6.2.3.2 Step 2 of the 802.1D-1998 sprecification.
With the current implementation, when running with very large bridge diameters, convergance will not always occur even if a root bridge is configured to have a longer max age.
Tested successfully on bridge diameters of ~200.
--- net/bridge/br_stp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/bridge/br_stp.c +1 -1
@@ -209,7 +209,7 @@ static void br_record_config_information(struct net_bridge_port *p, p->designated_age = jiffies - bpdu->message_age;mod_timer (&p->message_age_timer, jiffies - + (p->br->max_age - bpdu->message_age)); + + (bpdu->max_age - bpdu->message_age)); }/* called under bridge lock */
Signature · 1 line
1.8.1.2
David Miller
maintainerFrom: Chris Healy <[email protected]>
Date: Wed, 11 Sep 2013 21:37:47 -0700
Quoted 11 lines
This changes the
message_age_timercalculation to use the BPDU's max age as opposed to the local bridge's max age. This is in accordance with section 8.6.2.3.2 Step 2 of the 802.1D-1998 sprecification.With the current implementation, when running with very large bridge diameters, convergance will not always occur even if a root bridge is configured to have a longer max age.
Tested successfully on bridge diameters of ~200.
Signed-off-by Chris Healy <[email protected]>
Applied and queued up for -stable, thanks!