Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751804AbZI0V5b (ORCPT ); Sun, 27 Sep 2009 17:57:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751127AbZI0V5b (ORCPT ); Sun, 27 Sep 2009 17:57:31 -0400 Received: from mk-filter-2-a-1.mail.uk.tiscali.com ([212.74.100.53]:61665 "EHLO mk-filter-2-a-1.mail.uk.tiscali.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750957AbZI0V5a (ORCPT ); Sun, 27 Sep 2009 17:57:30 -0400 X-Trace: 266686303/mk-filter-2.mail.uk.tiscali.com/B2C/$b2c-THROTTLED-DYNAMIC/b2c-CUSTOMER-DYNAMIC-IP/79.69.87.63/None/hugh.dickins@tiscali.co.uk X-SBRS: None X-RemoteIP: 79.69.87.63 X-IP-MAIL-FROM: hugh.dickins@tiscali.co.uk X-SMTP-AUTH: X-MUA: X-IP-BHB: Once X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvIEAIt8v0pPRVc//2dsb2JhbACBUNBZhB4F X-IronPort-AV: E=Sophos;i="4.44,461,1249254000"; d="scan'208";a="266686303" Date: Sun, 27 Sep 2009 22:57:29 +0100 (BST) From: Hugh Dickins X-X-Sender: hugh@sister.anvils To: Nick Piggin cc: Andi Kleen , Wu Fengguang , Andrew Morton , linux-mm@kvack.org, LKML Subject: Re: [RFC][PATCH] HWPOISON: remove the unsafe __set_page_locked() In-Reply-To: <20090927192251.GB6327@wotan.suse.de> Message-ID: References: <20090926031537.GA10176@localhost> <20090926190645.GB14368@wotan.suse.de> <20090926213204.GX30185@one.firstfloor.org> <20090927192251.GB6327@wotan.suse.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1442 Lines: 34 On Sun, 27 Sep 2009, Nick Piggin wrote: > On Sun, Sep 27, 2009 at 05:26:25PM +0100, Hugh Dickins wrote: > > > > I don't particularly like adding a GFP_LOCKED just for this, and I > > don't particularly like having to remember to unlock the thing on the > > various(?) error paths between getting the page and adding it to cache. > > God no, please no more crazy branches in the page allocator. > > I'm going to resubmit my patches to allow 0-ref page allocations, > so the pagecache will be able to work with those to do what we > want here. > > > But it is a good idea, and if doing it that way would really close a > > race window which checking page->mapping (or whatever) cannot (I'm > > simply not sure about that), then it would seem the best way to go. > > Yep, seems reasonable: the ordering is no technical burden, and a > simple comment pointing to hwpoison will keep it maintainable. You move from "God no" to "Yep, seems reasonable"! I think perhaps you couldn't bring yourself to believe that I was giving any support to Andi's GFP_LOCKED idea. Pretend I did not! I'll assume we stick with the "God no", and we'll see how what you come up with affects what they want. Hugh -- 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/