From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail144.messagelabs.com (mail144.messagelabs.com [216.82.254.51]) by kanga.kvack.org (Postfix) with ESMTP id 16A286B00A6 for ; Wed, 27 May 2009 16:16:58 -0400 (EDT) Date: Wed, 27 May 2009 13:14:37 -0700 From: Andrew Morton Subject: Re: [PATCH 0/2] Fixes for hugetlbfs-related problems on shared memory Message-Id: <20090527131437.5870e342.akpm@linux-foundation.org> In-Reply-To: <1243422749-6256-1-git-send-email-mel@csn.ul.ie> References: <1243422749-6256-1-git-send-email-mel@csn.ul.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: Mel Gorman Cc: mingo@elte.hu, stable@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, hugh.dickins@tiscali.co.uk, Lee.Schermerhorn@hp.com, kosaki.motohiro@jp.fujitsu.com, starlight@binnacle.cx, ebmunson@us.ibm.com, agl@us.ibm.com, apw@canonical.com, wli@movementarian.org List-ID: On Wed, 27 May 2009 12:12:27 +0100 Mel Gorman wrote: > The following two patches are required to fix problems reported by > starlight@binnacle.cx. The tests cases both involve two processes interacting > with shared memory segments backed by hugetlbfs. Thanks. Both of these address http://bugzilla.kernel.org/show_bug.cgi?id=13302, yes? I added that info to the changelogs, to close the loop. Ingo, I'd propose merging both these together rather than routing one via the x86 tree, OK? Question is: when? Are we confident enough to merge it into 2.6.30 now, or should we hold off for 2.6.30.1? I guess we have a week or more, and if the changes do break something, we can fix that in 2.6.30.1 ;) -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org