From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 89BA7C433F5 for ; Fri, 5 Nov 2021 11:07:29 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 48F9F6008E for ; Fri, 5 Nov 2021 11:07:29 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 48F9F6008E Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=xO8bLbfppJ5GeGibcI4bEKUL2fMBCaU4OsdGFD4Md90=; b=ZsRYsXp/gEIxm9 SK15obAlKDLGfEb9ir8lxwuG5JR4Bzz48mKwp1r8raTPQxmBcmUT3QUvlUA6F/zBWjPzcUSQ5Qkeq 0zp89qDPnYPI8ZrjWtxZOgQmPK2Gi/a9JRwebOs1yFQrYpqaHiZ3vt6HpfCL17iDVeGl/A+ezELiG mHCY8LeLcf6YGkyL56xKHiBKXfSjFn51N8PwFneLbF2EvcvjOplClsWPpUvjNc7nucK+xIXWeXUk5 Grq5HgJkGl51JiFBIx29yoNTDzkGswN0pehakeozolGVlm1NhcnnA5o0VJNMHE+w7T3QG8q59RXnE yosdYMj2KPA1OKvZheuw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mix2w-00BAhM-Ap; Fri, 05 Nov 2021 11:06:10 +0000 Received: from mail.kernel.org ([198.145.29.99]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1mix2s-00BAge-Ic for linux-arm-kernel@lists.infradead.org; Fri, 05 Nov 2021 11:06:07 +0000 Received: by mail.kernel.org (Postfix) with ESMTPSA id 9EBBF6008E; Fri, 5 Nov 2021 11:06:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1636110366; bh=gJsm1IizLqHIU46nqJ2PCv1weO5m/+2Lhx/GTelVNiA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=uKknH7Xo3L4tFaDX1x10uGTlyVBD8Pp4ABE1Nd6UfR4udeBpijbZRzg2e/wl1LBDi oU7vKRK6ylEEkUbz6G2lXztI5Z56Z1/C/jWh2euo0IRIb3z9doWrztVJuejnH4XNmj wp4FYpWDS3vR91479Qi8qBmLwsxkXj7gfKB/NXKB3TxhGj432VRQBMAwsWVifm5OM2 lz8EeR9tRp8idUnHCk47LG7uL5nCfRzH7+qg4g+dUTx9rWnMVGRk57ujHNhiyIRqLI adN/QVDYKJsQ+S1aOJLIsJeEn+hkIu2Bhltdxbjdhm0TYWiCeTGdQgesPgunBPQ3ow zGCcD9kAFT/NQ== Date: Fri, 5 Nov 2021 13:05:58 +0200 From: Mike Rapoport To: Catalin Marinas Cc: Qian Cai , Will Deacon , Andrew Morton , linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] arm64: Track no early_pgtable_alloc() for kmemleak Message-ID: References: <20211104155623.11158-1-quic_qiancai@quicinc.com> <9bb6fe11-c10a-a373-9288-d44a5ba976fa@quicinc.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20211105_040606_657270_239DF8DB X-CRM114-Status: GOOD ( 27.78 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Nov 05, 2021 at 10:08:05AM +0000, Catalin Marinas wrote: > On Thu, Nov 04, 2021 at 01:57:03PM -0400, Qian Cai wrote: > > On 11/4/21 1:06 PM, Mike Rapoport wrote: > > > I think I'll be better to rename MEMBLOCK_ALLOC_KASAN to, say, > > > MEMBLOCK_ALLOC_NOKMEMLEAK and use that for both KASAN and page table cases. > > > > Okay, that would look a bit nicer. > > Or MEMBLOCK_ALLOC_ACCESSIBLE_NOLEAKTRACE to match SLAB_NOLEAKTRACE and > also hint that it's accessible memory. Hmm, I think MEMBLOCK_ALLOC_NOLEAKTRACE is enough. Having a constant instead of end limit already implies there is no limit and when we update the API to use lower bits or a dedicated 'flags' we won't need to change the flag name as well. > > > But more generally, we are going to hit this again and again. > > > Couldn't we add a memblock allocation as a mean to get more memory to > > > kmemleak::mem_pool_alloc()? > > > > For the last 5 years, this is the second time I am ware of this kind of > > issue just because of the 64KB->4KB switch on those servers, although I > > agree it could happen again in the future due to some new debugging > > features etc. I don't feel a strong need to rewrite it now though. Not > > sure if Catalin saw things differently. Anyway, Mike, do you agree that > > we could rewrite that separately in the future? > > I was talking to Mike on IRC last night and I think you still need a > flag, otherwise you could get a recursive memblock -> kmemleak -> > memblock call (that's why we have SLAB_NOLEAKTRACE). So for the time > being, a new MEMBLOCK_* definition would do. > > I wonder whether we could actually use the bottom bits in the end/limit > as actual flags so one can do (MEMBLOCK_ALLOC_ACCESSIBLE | > MEMBLOCK_NOLEAKTRACE). But that could be for a separate clean-up. We never restricted end/limit to be on a word boundary, but I doubt that in practice we'd ever have the low bits set. I'm not entirely happy with using end limit parameter for this, I'd like to see how much churn it will be to extend some of memblock_*_alloc with an explicit flags parameter. -- Sincerely yours, Mike. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel