On Sat, May 26, 2012 at 11:01:40PM +0100, Ben Hutchings wrote: > On Fri, 2012-05-18 at 14:27 -0700, Greg KH wrote: > > 3.3-stable review patch. If anyone has any objections, please let me know. > > > > ------------------ > > > > From: Catalin Marinas <[email protected]> > > > > commit 100d13c3b5b9410f604b86f5e0a34da64b8cf659 upstream. > > > > Kmemleak tracks the percpu allocations via a specific API and the > > originally allocated areas must be removed from kmemleak (via > > kmemleak_free). The code was already doing this for SMP systems. > > > > Reported-by: Sami Liedes <[email protected]> > > Cc: Tejun Heo <[email protected]> > > Cc: Christoph Lameter <[email protected]> > > Signed-off-by: Catalin Marinas <[email protected]> > > Signed-off-by: Tejun Heo <[email protected]> > > Signed-off-by: Greg Kroah-Hartman <[email protected]> > [...] > > Is this wanted for 3.2.y as well?
No, as it depends on commit f528f0b8 (kmemleak: Handle percpu memory allocation) which was merged in 3.3. -- Catalin -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
