Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759543Ab2JaSaW (ORCPT ); Wed, 31 Oct 2012 14:30:22 -0400 Received: from mail-ia0-f174.google.com ([209.85.210.174]:55142 "EHLO mail-ia0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751269Ab2JaSaU (ORCPT ); Wed, 31 Oct 2012 14:30:20 -0400 MIME-Version: 1.0 In-Reply-To: <1351241323.12171.43.camel@twins> References: <20121008150949.GA15130@redhat.com> <20121017040515.GA13505@redhat.com> <1351167554.23337.14.camel@twins> <1351175972.12171.14.camel@twins> <1351241323.12171.43.camel@twins> From: Sasha Levin Date: Wed, 31 Oct 2012 14:29:59 -0400 Message-ID: Subject: Re: [patch for-3.7] mm, mempolicy: fix printing stack contents in numa_maps To: Peter Zijlstra Cc: Linus Torvalds , David Rientjes , Mel Gorman , Rik van Riel , Dave Jones , Andrew Morton , KOSAKI Motohiro , bhutchings@solarflare.com, Konstantin Khlebnikov , Naoya Horiguchi , Hugh Dickins , KAMEZAWA Hiroyuki , linux-kernel@vger.kernel.org, linux-mm@kvack.org 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: 1517 Lines: 39 On Fri, Oct 26, 2012 at 4:48 AM, Peter Zijlstra wrote: > On Thu, 2012-10-25 at 16:09 -0700, Linus Torvalds wrote: >> On Thu, Oct 25, 2012 at 7:39 AM, Peter Zijlstra wrote: >> > >> > So I think the below should work, we hold the spinlock over both rb-tree >> > modification as sp free, this makes mpol_shared_policy_lookup() which >> > returns the policy with an incremented refcount work with just the >> > spinlock. >> > >> > Comments? >> >> Looks reasonable, if annoyingly complex for something that shouldn't >> be important enough for this. Oh well. > > I agree with that.. Its just that when doing numa placement one needs to > respect the pre-existing placement constraints. I've not seen a way > around this. > >> However, please check me on this: the need for this is only for >> linux-next right now, correct? All the current users in my tree are ok >> with just the mutex, no? > > Yes, the need comes from the numa stuff and I'll stick this patch in > there. > > I completely missed Mel's patch turning it into a mutex, but I guess > that's what -next is for :-). So I've been fuzzing with it for the past couple of days and it's been looking fine with it. Can someone grab it into his tree please? Thanks, Sasha -- 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/