| 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: <20110106155335.GC30150@windriver.com> Date: Thu, 6 Jan 2011 10:53:35 -0500 From: Paul Gortmaker <paul.gortmaker@...driver.com> To: Jiri Slaby <jirislaby@...il.com> Cc: stable@...nel.org, linux-kernel@...r.kernel.org, stable-review@...nel.org, Andi Kleen <andi@...stfloor.org>, Greg KH <gregkh@...e.de> Subject: Re: [34-longterm 000/260] v2.6.34.8 longterm review [Re: [34-longterm 000/260] v2.6.34.8 longterm review] On 06/01/2011 (Thu 13:47) Jiri Slaby wrote: > CCing: > gregkh (32-stable) > ak (35-stable) > > On 01/04/2011 08:11 PM, Paul Gortmaker wrote: > > If you want to look around at what else is in "next_round" you can grab > > the queue from: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/longterm/longterm-queue-2.6.34.git > > > > Let me know if you still think something is missing, and/or call out the > > upstream commit IDs explicitly and I'll do the right thing. > > Hi, > e2efafbf139d2bfdfe96f2901f03189fecd172e4 > is still missing (I've just checked SLE11SP1 and openSUSE 11.3, which is > based on .32 and .34 respectively and the problem is easily reproducible > there). It is trivial to be backported. Thanks, it does look like a candidate for adding to next_round. P. > > thanks, > -- > js -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists