Received: by 10.192.165.148 with SMTP id m20csp4674826imm; Tue, 24 Apr 2018 06:44:23 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/035VQ0WxuDV0MWuYA1erUuOi41qLv2zpl//ADHo50PFdsUBjcoZT35ys7Fq0J7Xtm2FBt X-Received: by 10.99.185.8 with SMTP id z8mr20357286pge.436.1524577463651; Tue, 24 Apr 2018 06:44:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524577463; cv=none; d=google.com; s=arc-20160816; b=EIQj6sSgieUmpQzNcbtOOuwBC0YytEEIrQfj8jV5fsbglzZ+2IXMIbTSABb9mZvtOu NTcXJLRymsDXVdRSvBuyM0KnmQ8kvCoYD97WiBVrqwvgc6dtJVaeB6a3ui2kuMT7aB36 C20pEnClY/DDZ9qaRQsiS86D3rTfOIrqfvk4HS754qv0lhJkWme4hMbaFyDV9aSNqiwm c66tG8GVXYB8OTPMhxIpt01bxVbwuxQi05n5ibzQc0BblPm5DoCWq8gGxViKuPRDE9uD G4HPBFJBiAVWvHQVB+xneL46qmiws7nxp8jNwC8AM5VIo4SfADVPxjgJ96e6Vks/MF+3 uL+A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=GkQtdc+dEA9Pwt/I4MAs7mHk6dZ4XES7nRHA/75CXNc=; b=FMt2OBRpyPLeHo0YlUe1pHjgU6e2rdXhoUnOwovA9Z5ig3xKE4gIlZARK+rEvbb++b 3rbKcy+j7jtFfoznIatH/qOsB9qgeCT7KH2nZuh4DR+8929/2ZNX71p1B8xWKZhQGZkp aGFAwGLIPP9COlPpVKK38L7CFvzKEZ+85TzHpRyU1semkYgYcwCBkcV7kNyp+NQ4nOMO Qnc1YwjO1j9fjYjXIGG1g9UABqfpGraJRmzOD47upDBhaOVuQ9RmkOdAT+ewS3T3bzHg YCzEiqrzpAoOcf+8OGLmqlBqLMpMSmym/wD1/l1T8gXY2mTkPfwhBvhTX08oaoN4Dkgc 7Wkw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l19si13471472pfg.17.2018.04.24.06.44.09; Tue, 24 Apr 2018 06:44:23 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934484AbeDXNlz (ORCPT + 99 others); Tue, 24 Apr 2018 09:41:55 -0400 Received: from foss.arm.com ([217.140.101.70]:53528 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933173AbeDXNlw (ORCPT ); Tue, 24 Apr 2018 09:41:52 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id A4C7E80D; Tue, 24 Apr 2018 06:41:52 -0700 (PDT) Received: from armageddon.cambridge.arm.com (armageddon.cambridge.arm.com [10.1.206.84]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 5023C3F4FF; Tue, 24 Apr 2018 06:41:51 -0700 (PDT) Date: Tue, 24 Apr 2018 14:41:48 +0100 From: Catalin Marinas To: Michal Hocko Cc: Chunyu Hu , Dmitry Vyukov , Chunyu Hu , LKML , Linux-MM Subject: Re: [RFC] mm: kmemleak: replace __GFP_NOFAIL to GFP_NOWAIT in gfp_kmemleak_mask Message-ID: <20180424134148.qkvqqa4c37l6irvg@armageddon.cambridge.arm.com> References: <1524243513-29118-1-git-send-email-chuhu@redhat.com> <20180420175023.3c4okuayrcul2bom@armageddon.cambridge.arm.com> <20180422125141.GF17484@dhcp22.suse.cz> <20180424132057.GE17484@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180424132057.GE17484@dhcp22.suse.cz> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 24, 2018 at 07:20:57AM -0600, Michal Hocko wrote: > On Mon 23-04-18 12:17:32, Chunyu Hu wrote: > [...] > > So if there is a new flag, it would be the 25th bits. > > No new flags please. Can you simply store a simple bool into fail_page_alloc > and have save/restore api for that? For kmemleak, we probably first hit failslab. Something like below may do the trick: diff --git a/mm/failslab.c b/mm/failslab.c index 1f2f248e3601..63f13da5cb47 100644 --- a/mm/failslab.c +++ b/mm/failslab.c @@ -29,6 +29,9 @@ bool __should_failslab(struct kmem_cache *s, gfp_t gfpflags) if (failslab.cache_filter && !(s->flags & SLAB_FAILSLAB)) return false; + if (s->flags & SLAB_NOLEAKTRACE) + return false; + return should_fail(&failslab.attr, s->object_size); } Can we get a second should_fail() via should_fail_alloc_page() if a new slab page is allocated? -- Catalin