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: Sun, 6 Mar 2011 02:03:28 -0600 From: Adam Majer <adamm@...bino.com> To: Stephen Hemminger <stephen.hemminger@...tta.com> Cc: "David S. Miller" <davem@...emloft.net>, Alexey Kuznetsov <kuznet@....inr.ac.ru>, "Pekka Savola (ipv6)" <pekkas@...core.fi>, James Morris <jmorris@...ei.org>, Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>, Patrick McHardy <kaber@...sh.net>, bridge@...ts.linux-foundation.org, netdev@...r.kernel.org Subject: Re: [PATCH 1/2] Issue NETDEV_CHANGE notification when bridge changes state On Sat, Mar 05, 2011 at 10:43:03PM -0800, Stephen Hemminger wrote: > Why not set forwarding delay to zero? I don't think you are using STP? > > P.s: removing linux-kernel mailing list, since there is no point > in copying the whole world on this thread. I just sent patches where MAINTAINERS file told me to send it. ;) No, I'm not relying on STP. I think setting learning->forwarding delay to 0 could cause problems with STP like loops until the loop is detected. There may be a better spot where to insert the notification that the bridge is forwarding data, though I'm not exactly certain where. The patch will cause bridge to issue NETDEV_CHANGE notification for all topology changes. This may or may not be useful but shouldn't be harmful (I can't imagine these occur very often?) The IPv6 autoconf patch will only act on this if it doesn't have IPv6 address configured manually or via autoconf. -- Adam Majer adamm@...bino.com -- 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
Powered by blists - more mailing lists