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 X-Spam-Level: X-Spam-Status: No, score=-8.7 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,UNPARSEABLE_RELAY,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 230BAC433E0 for ; Tue, 16 Mar 2021 16:41:20 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 8DB2265107 for ; Tue, 16 Mar 2021 16:41:19 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8DB2265107 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 21DFA6B006E; Tue, 16 Mar 2021 12:41:19 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 1CDE76B0070; Tue, 16 Mar 2021 12:41:19 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 0951C6B0071; Tue, 16 Mar 2021 12:41:19 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0245.hostedemail.com [216.40.44.245]) by kanga.kvack.org (Postfix) with ESMTP id E1DBD6B006E for ; Tue, 16 Mar 2021 12:41:18 -0400 (EDT) Received: from smtpin28.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with ESMTP id 86A5E8249980 for ; Tue, 16 Mar 2021 16:41:18 +0000 (UTC) X-FDA: 77926302636.28.04A6F4B Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by imf12.hostedemail.com (Postfix) with ESMTP id 5824D2BCB for ; Tue, 16 Mar 2021 16:41:12 +0000 (UTC) X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id BAAF8AC24; Tue, 16 Mar 2021 16:41:03 +0000 (UTC) Received: from localhost (brahms [local]) by brahms (OpenSMTPD) with ESMTPA id 924d4c15; Tue, 16 Mar 2021 16:42:18 +0000 (UTC) Date: Tue, 16 Mar 2021 16:42:18 +0000 From: Luis Henriques To: Alexander Potapenko , Marco Elver , Dmitry Vyukov , Catalin Marinas Cc: Andrew Morton , kasan-dev@googlegroups.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Issue with kfence and kmemleak Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-Stat-Signature: 3o57q5csxpsogwsgnan4odzdxnyfst1e X-Rspamd-Server: rspam01 X-Rspamd-Queue-Id: 5824D2BCB Received-SPF: none (suse.de>: No applicable sender policy available) receiver=imf12; identity=mailfrom; envelope-from=""; helo=mx2.suse.de; client-ip=195.135.220.15 X-HE-DKIM-Result: none/none X-HE-Tag: 1615912872-356160 Content-Transfer-Encoding: quoted-printable X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: Hi! This is probably a known issue, but just in case: looks like it's not possible to use kmemleak when kfence is enabled: [ 0.272136] kmemleak: Cannot insert 0xffff888236e02f00 into the object= search tree (overlaps existing) [ 0.272136] CPU: 0 PID: 8 Comm: kthreadd Not tainted 5.12.0-rc3+ #92 [ 0.272136] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIO= S rel-1.14.0-0-g155821a-rebuilt.opensuse.org 04/01/2014 [ 0.272136] Call Trace: [ 0.272136] dump_stack+0x6d/0x89 [ 0.272136] create_object.isra.0.cold+0x40/0x62 [ 0.272136] ? process_one_work+0x5a0/0x5a0 [ 0.272136] ? process_one_work+0x5a0/0x5a0 [ 0.272136] kmem_cache_alloc_trace+0x110/0x2f0 [ 0.272136] ? process_one_work+0x5a0/0x5a0 [ 0.272136] kthread+0x3f/0x150 [ 0.272136] ? lockdep_hardirqs_on_prepare+0xd4/0x170 [ 0.272136] ? __kthread_bind_mask+0x60/0x60 [ 0.272136] ret_from_fork+0x22/0x30 [ 0.272136] kmemleak: Kernel memory leak detector disabled [ 0.272136] kmemleak: Object 0xffff888236e00000 (size 2097152): [ 0.272136] kmemleak: comm "swapper", pid 0, jiffies 4294892296 [ 0.272136] kmemleak: min_count =3D 0 [ 0.272136] kmemleak: count =3D 0 [ 0.272136] kmemleak: flags =3D 0x1 [ 0.272136] kmemleak: checksum =3D 0 [ 0.272136] kmemleak: backtrace: [ 0.272136] memblock_alloc_internal+0x6d/0xb0 [ 0.272136] memblock_alloc_try_nid+0x6c/0x8a [ 0.272136] kfence_alloc_pool+0x26/0x3f [ 0.272136] start_kernel+0x242/0x548 [ 0.272136] secondary_startup_64_no_verify+0xb0/0xbb I've tried the hack below but it didn't really helped. Obviously I don't really understand what's going on ;-) But I think the reason for this patch not working as (I) expected is because kfence is initialised *before* kmemleak. diff --git a/mm/kfence/core.c b/mm/kfence/core.c index 3b8ec938470a..b4ffd7695268 100644 --- a/mm/kfence/core.c +++ b/mm/kfence/core.c @@ -631,6 +631,9 @@ void __init kfence_alloc_pool(void) =20 if (!__kfence_pool) pr_err("failed to allocate pool\n"); + kmemleak_no_scan(__kfence_pool); } Cheers, -- Lu=EDs