netdev - Re: bridge: Clamp forward_delay when enabling STP

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] [day] [month] [year] [list]

Message-Id: <20130912.233233.870577692268998436.davem@davemloft.net>
Date:	Thu, 12 Sep 2013 23:32:33 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	herbert@...dor.apana.org.au
Cc:	shemminger@...tta.com, netdev@...r.kernel.org
Subject: Re: bridge: Clamp forward_delay when enabling STP

From: Herbert Xu <herbert@...dor.apana.org.au>
Date: Thu, 12 Sep 2013 17:12:05 +1000

> At some point limits were added to forward_delay.  However, the
> limits are only enforced when STP is enabled.  This created a
> scenario where you could have a value outside the allowed range
> while STP is disabled, which then stuck around even after STP
> is enabled.
> 
> This patch fixes this by clamping the value when we enable STP.
> 
> I had to move the locking around a bit to ensure that there is
> no window where someone could insert a value outside the range
> while we're in the middle of enabling STP.
> 
> Signed-off-by: Herbert Xu <herbert@...dor.apana.org.au>

Applied and queued up for -stable, thanks Herbert.
--
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