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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 13 Apr 2022 12:12:55 +0200 From: Joachim Wiberg <troglobit@...il.com> To: Nikolay Aleksandrov <razor@...ckwall.org>, Roopa Prabhu <roopa@...dia.com> Cc: netdev@...r.kernel.org, bridge@...ts.linux-foundation.org, "David S . Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, Tobias Waldekranz <tobias@...dekranz.com>, Vladimir Oltean <vladimir.oltean@....com> Subject: Re: [PATCH RFC net-next 08/13] net: bridge: avoid classifying unknown multicast as mrouters_only On Wed, Apr 13, 2022 at 12:00, Nikolay Aleksandrov <razor@...ckwall.org> wrote: > On 13/04/2022 11:55, Nikolay Aleksandrov wrote: >> On 13/04/2022 11:51, Joachim Wiberg wrote: >>> So, if I add a bridge flag, default off as you mentioned out earlier, >>> which changes the default behavior of MCAST_FLOOD, then you'd be OK with >>> that? Something cheeky like this perhaps: >>> if (!ipv4_is_local_multicast(ip_hdr(skb)->daddr)) >>> BR_INPUT_SKB_CB(skb)->mrouters_only = !br_opt_get(br, BROPT_MCAST_FLOOD_RFC4541); >> Exactly! And that is exactly what I had in mind when I wrote it. :) Awesome, thank you! :) > Just please use a different option name that better suggests what it does. Heh, yeah spent a good while with my colleague (Tobias) thinking about how to name this one. I'll see what I can come up with, but whatever shows up in the next patch iteration will be very open for discussion. Cheers /Joachim
Powered by blists - more mailing lists