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: Fri, 22 Jun 2012 08:16:50 -0700 From: Greg KH <gregkh@...uxfoundation.org> To: Mike Snitzer <snitzer@...hat.com> Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org, torvalds@...ux-foundation.org, akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk, Joe Thornber <ejt@...hat.com>, Alasdair G Kergon <agk@...hat.com> Subject: Re: [PATCH] dm thin: reinstate missing mempool_free in cell_release_singleton On Fri, Jun 22, 2012 at 10:59:48AM -0400, Mike Snitzer wrote: > Hi Greg, > > 3.3-stable pulled in upstream commit > 6f94a4c45a6f744383f9f695dde019998db3df55 (dm thin: fix stacked bi_next usage) > > But later in the 3.4 development window it was determined that that > commit introduced a significant leak. The following upstream commit > fixes it (but unfortunately didn't cc: stable). 3.3 is end-of-life, so there's not much I can do with the 3.3-stable tree anymore, sorry. If there's any other tree I should apply this to that is active (i.e. 3.0 or 3.4), please let me know. sorry, greg k-h -- 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