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
| ||
|
Date: Tue, 02 Oct 2018 22:27:51 -0700 (PDT) From: David Miller <davem@...emloft.net> To: idosch@...lanox.com Cc: netdev@...r.kernel.org, nikolay@...ulusnetworks.com, roopa@...ulusnetworks.com, bridge@...ts.linux-foundation.org, mlxsw@...lanox.com Subject: Re: [PATCH net-next] bridge: mcast: Default back to multicast enabled state From: Ido Schimmel <idosch@...lanox.com> Date: Mon, 1 Oct 2018 11:57:01 +0300 > Commit 13cefad2f2c1 ("net: bridge: convert and rename mcast disabled") > converted the 'multicast_disabled' field to an option bit named > 'BROPT_MULTICAST_ENABLED'. > > While the old field was implicitly initialized to 0, the new field is > not initialized, resulting in the bridge defaulting to multicast > disabled state and breaking existing applications. > > Fix this by explicitly initializing the option. > > Fixes: 13cefad2f2c1 ("net: bridge: convert and rename mcast disabled") > Signed-off-by: Ido Schimmel <idosch@...lanox.com> Applied.
Powered by blists - more mailing lists