| 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: <20090707.183440.214607665.davem@davemloft.net> Date: Tue, 07 Jul 2009 18:34:40 -0700 (PDT) From: David Miller <davem@...emloft.net> To: lk-netdev@...netdev.nosense.org Cc: netdev@...r.kernel.org, pekkas@...core.fi, yoshfuji@...ux-ipv6.org Subject: Re: [patch] ipv6: correct return on ipv6_rcv() packet drop From: Mark Smith <lk-netdev@...netdev.nosense.org> Date: Wed, 8 Jul 2009 06:34:13 +0930 > On Tue, 07 Jul 2009 08:52:19 -0700 (PDT) > David Miller <davem@...emloft.net> wrote: > >> From: Mark Smith <lk-netdev@...netdev.nosense.org> >> Date: Tue, 7 Jul 2009 18:50:15 +0930 >> >> > Today I came across this earlier partial version of what I >> > independently identified and submitted, so I shouldn't get full credit >> > for it: >> > >> > http://lkml.indiana.edu/hypermail/linux/kernel/0804.1/2393.html >> >> I already pushed your change out to my public tree so we're >> past the point of being able to modify the commit message. >> >> We'll just try to be more careful next time. > > Is there an easier way to avoid this, other than a google search? I > happened to discover it by doing a google search when I was at work, to > see how my patch was going. I suppose possibly not. Perhaps some day we can have more powerful searching mechanisms on patchwork, who knows. Feel free to discuss such ideas on the patchwork mailing list: https://ozlabs.org/mailman/listinfo/patchwork -- 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