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
| ||
|
Message-ID: <20101217100101.5e6e6708@nehalam> Date: Fri, 17 Dec 2010 10:01:01 -0800 From: Stephen Hemminger <shemminger@...tta.com> To: David Miller <davem@...emloft.net> Cc: netdev@...r.kernel.org Subject: Re: [PATCH net-next] ipv6: remove duplicate neigh_ifdown On Fri, 17 Dec 2010 09:49:16 -0800 (PST) David Miller <davem@...emloft.net> wrote: > From: Stephen Hemminger <shemminger@...tta.com> > Date: Thu, 16 Dec 2010 19:42:54 -0800 > > > When device is being set to down, neigh_ifdown was being called > > twice. Once from addrconf notifier and once from ndisc notifier. > > > > Signed-off-by: Stephen Hemminger <shemminger@...tta.com> > > I'll give you a cookie if you can show me how this patch applies to > net-next-2.6 cleanly. :-) > > It only matches the code in net-2.6 which has changed non-trivially in > net-next-2.6 > > If you worked against net-2.6 and thought "I can't think of anything > that could have changed in net-next-2.6 in this area", that's not > an appropriate way to operate and submit patches. > > Please don't be so careless, thanks. Ok. It followed my last patch that did the rt6_ifdown only if not loopback. Since you accepted that, I sent the next one. -- -- 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