Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757487Ab2E3S1F (ORCPT ); Wed, 30 May 2012 14:27:05 -0400 Received: from mail-we0-f174.google.com ([74.125.82.174]:34164 "EHLO mail-we0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757272Ab2E3S1D (ORCPT ); Wed, 30 May 2012 14:27:03 -0400 MIME-Version: 1.0 In-Reply-To: <1338368529-21784-1-git-send-email-kosaki.motohiro@gmail.com> References: <1338368529-21784-1-git-send-email-kosaki.motohiro@gmail.com> From: Linus Torvalds Date: Wed, 30 May 2012 11:26:41 -0700 X-Google-Sender-Auth: IowvCgMEcbudX3u4qVNxi9YB53w Message-ID: Subject: Re: [PATCH 0/6] mempolicy memory corruption fixlet To: kosaki.motohiro@gmail.com Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, Andrew Morton , Dave Jones , Mel Gorman , Christoph Lameter , stable@vger.kernel.org, hughd@google.com, KOSAKI Motohiro Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 779 Lines: 19 On Wed, May 30, 2012 at 2:02 AM, wrote: > > So, I think we should reconsider about shared mempolicy completely. Quite frankly, I'd prefer that approach. The code is subtle and horribly bug-fraught, and I absolutely detest the way it looks too. Reading your patches was actually somewhat painful. If we could just remove the support for it entirely, that would be *much* preferable to continue working with this code. Could we just try that removal, and see if anybody screams? Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/