linux-kernel - Re: [stable] [PATCH 0/3] Reduce watermark-related problems with the per-cpu allocator V4

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20100924091412.GA8187@csn.ul.ie>
Date:	Fri, 24 Sep 2010 10:14:12 +0100
From:	Mel Gorman <mel@....ul.ie>
To:	Greg KH <greg@...ah.com>
Cc:	Rik van Riel <riel@...hat.com>,
	Christoph Lameter <cl@...ux-foundation.org>,
	Dave Chinner <david@...morbit.com>,
	Linux Kernel List <linux-kernel@...r.kernel.org>,
	linux-mm@...ck.org, Minchan Kim <minchan.kim@...il.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Johannes Weiner <hannes@...xchg.org>,
	Andrew Morton <akpm@...ux-foundation.org>, stable@...nel.org,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: [stable] [PATCH 0/3] Reduce watermark-related problems with
	the per-cpu allocator V4

> > > <SNIP>
> > > If so, for which -stable tree?  .27, .32, and .35 are all
> > > currently active.
> > > 
> > 
> > 2.6.35 for certain.
> > 
> > I would have a strong preference for 2.6.32 as well as it's a baseline for
> > a number of distros. The second commit will conflict with per-cpu changes
> > but the resolution is straight-forward.
> 
> Thanks for the backport, I've queued these up for .32 and .35 now.
> 

Thanks Greg.

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab
--
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/