| 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: <4D9309B4.2000501@parallels.com> Date: Wed, 30 Mar 2011 05:45:08 -0500 From: Rob Landley <rlandley@...allels.com> To: David Miller <davem@...emloft.net> CC: <linux-kernel@...r.kernel.org>, <containers@...ts.linux-foundation.org>, <netdev@...r.kernel.org>, <stable@...nel.org> Subject: Re: 2.6.38 containers bug: Infinite loop in /proc/sys/net/ipv6/neigh/neigh/neigh... On 03/30/2011 05:35 AM, David Miller wrote: > From: Rob Landley <rlandley@...allels.com> > Date: Wed, 30 Mar 2011 05:16:19 -0500 > >> Pinging the stable guys to make sure this goes in a dot release. > > Please do not do this. Too late, but presumably they got your NAK. > I let fixes soak in Linus's tree for a week or even more before I submit > them to -stable. So you think letting it soak in the merge window and the churn of -rc1 (which currently doesn't boot for me due to an ide issue) will provide more validity than a specific "There was an infinite loop in the filesystem, there is now no longer an infinite loop in the filesystem, here's the specific test for it" and visual inspection ofthe patch? *shrug* I hear what you say. It's certainly a point of view. Rob -- 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