netdev - Re: [PATCH] bridge: push blocking slaves to forwarding when turning stp off

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111213161613.0c59ab36@nehalam.linuxnetplumber.net>
Date:	Tue, 13 Dec 2011 16:16:13 -0800
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Vitalii Demianets <vitas@...factor.kiev.ua>
Cc:	netdev@...r.kernel.org, bridge@...ts.linux-foundation.org,
	Michael Tremer <michael.tremer@...ire.org>
Subject: Re: [PATCH] bridge: push blocking slaves to forwarding when turning
 stp off

On Tue, 13 Dec 2011 11:36:25 +0200
Vitalii Demianets <vitas@...factor.kiev.ua> wrote:

> If there is a slave in blocking state when stp is turned off, that slave will 
> remain in blocking state for indefinitely long time until interface state 
> changed. We should push all blocking slaves into forwarding state after 
> turning stp off.
> 
> Signed-off-by: Vitalii Demianets <vitas@...factor.kiev.ua>

Maybe. But if the port was in the blocking state then STP must have
decided there was a loop in the network if that port was used.
Therefore blindly putting the port into forwarding state could cause
disastrous network flood.


The user can force the port back out of blocking state (via sysfs).

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html