linux-kernel - Re: [PATCHv3 net-next] bridge: allow setting hash_max + multicast

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: <20150525.172818.2000334376621437405.davem@davemloft.net>
Date:	Mon, 25 May 2015 17:28:18 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	linus.luessing@...3.blue
Cc:	netdev@...r.kernel.org, bridge@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org, stephen@...workplumber.org,
	herbert@...dor.apana.org.au, roopa@...ulusnetworks.com,
	cwang@...pensource.com, sashok@...ulusnetworks.com,
	wkok@...ulusnetworks.com
Subject: Re: [PATCHv3 net-next] bridge: allow setting hash_max +
 multicast_router if interface is down

From: Linus Lüssing <linus.luessing@...3.blue>
Date: Sat, 23 May 2015 03:12:34 +0200

> Network managers like netifd (used in OpenWRT for instance) try to
> configure interface options after creation but before setting the
> interface up.
> 
> Unfortunately the sysfs / bridge currently only allows to configure the
> hash_max and multicast_router options when the bridge interface is up.
> But since br_multicast_init() doesn't start any timers and only sets
> default values and initializes timers it should be save to reconfigure
> the default values after that, before things actually get active after
> the bridge is set up.
> 
> Signed-off-by: Linus Lüssing <linus.luessing@...3.blue>

Applied to net-next, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/