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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id 632C7C00140 for ; Mon, 15 Aug 2022 12:48:37 +0000 (UTC) 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=qBDQjBH126iPkF3oRzPH7zn9cohUoP5svBhd9dyeuFo=; b=c2gAjYWiCWI6Nj 0KB3JicBiwQutrf0MOWVmU/jaZlE7xN34k5LTSON0R5nVpikLMHdrDxiFAgM4YI5Hn5vkUc2bX45y tf0lw0GoR54ZAuoVDk1vVT885kC1FqLIN8TX//E8K4IkY31XnQsuckE0z6HcM/3jrkAVlGTMFpl1V VmC8DFsxhueV7tsltJG/wQZH2X9NTcdk6X6ygl3e2z42agdUVjOh7HItAxPxxrZJauQIwmPGfK+ff CU/27BI5QOzi3c6gqK4bEFFdaR5BrPTqILcLbHRLNE+GmEhMRZc7nyZ2J2uiPyWQkC1PCEqKndpwG L2gPKw2eWBorodYKXS0A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oNZVA-00GK09-UC; Mon, 15 Aug 2022 12:47:30 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oNZUv-00GJn6-04 for linux-arm-kernel@lists.infradead.org; Mon, 15 Aug 2022 12:47:15 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 56A35611C2; Mon, 15 Aug 2022 12:47:12 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1EC1DC433B5; Mon, 15 Aug 2022 12:47:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1660567631; bh=xzfMfa6CNdSnxRnNe2T0XGMIAiUHZhRQJY8MyHI/FMo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=T9p8KoYd9JGYgvaujbFU1eulqVF93hz5sI35hpf5iHYPBDnMZC4yM3Ef2/T4SlVpF Fq/I1syWIVtHssfHl743u3qRYoJ3ODJ9ygmSq2X8EnhTItrQ+Pb3HjS05fHtxO+ik5 RTWGVvTI6vOcxALx7j1q7rhXFXmVXNGAsgcSba5L8ZmAnn75zsiCkoTWW/HgMtvacG t6RitK0zHbKdZNSYRY0XM3MM5XYTT8In83Q91EEHAPi5k/AG3QMqDVyXeoHjTLLcBS UtagKpOjSLokF91sb8oA8nik4A+T9PGntCfdG0e/wM38/KGA7DpUH4OEm+7Pf0HBTP sXtKFwo2uIRig== Date: Mon, 15 Aug 2022 13:47:06 +0100 From: Will Deacon To: Max Schulze Cc: linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com, naush@raspberrypi.com, glider@google.com, elver@google.com, dvyukov@google.com, kasan-dev@googlegroups.com Subject: Re: kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) [RPi CM4] Message-ID: <20220815124705.GA9950@willie-the-truck> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220815_054713_322738_A44D2006 X-CRM114-Status: GOOD ( 14.86 ) 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 [+kfence folks as kfence_alloc_pool() is starting the stacktrace] On Mon, Aug 15, 2022 at 11:52:05AM +0200, Max Schulze wrote: > Hello, > > I get these messages when booting 5.19.0 on RaspberryPi CM4. > > Full boot log is at https://pastebin.ubuntu.com/p/mVhgBwxqPj/ > > Anyone seen this? What can I do ? > > Thanks, > > Max > > > [0.087630] kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) > [0.087756] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.19.0-v8-0815+ #5 > [0.087836] Hardware name: Raspberry Pi Compute Module 4 Rev 1.0 (DT) > [0.087901] Call trace: > [0.087941] dump_backtrace.part.0+0x1dc/0x1ec > [0.088029] show_stack+0x24/0x80 > [0.088089] dump_stack_lvl+0x8c/0xb8 > [0.088161] dump_stack+0x1c/0x38 > [0.088224] create_object.isra.0+0x490/0x4b0 > [0.088298] kmemleak_alloc+0x3c/0x50 > [0.088365] kmem_cache_alloc+0x2f8/0x450 > [0.088435] __proc_create+0x18c/0x400 > [0.088509] proc_create_reg+0x54/0xd0 > [0.088569] proc_create_seq_private+0x94/0x120 > [0.088634] init_mm_internals+0x1d8/0x248 > [0.088704] kernel_init_freeable+0x188/0x388 > [0.088776] kernel_init+0x30/0x150 > [0.088837] ret_from_fork+0x10/0x20 > [0.088903] kmemleak: Kernel memory leak detector disabled > [0.088958] kmemleak: Object 0xffffff806e24d000 (size 2097152): > [0.089021] kmemleak: comm "swapper", pid 0, jiffies 4294892296 > [0.089085] kmemleak: min_count = -1 > [0.089131] kmemleak: count = 0 > [0.089174] kmemleak: flags = 0x5 > [0.089219] kmemleak: checksum = 0 > [0.089264] kmemleak: backtrace: > [0.089306] kmemleak_alloc_phys+0x94/0xb0 > [0.089379] memblock_alloc_range_nid+0x1c0/0x20c > [0.089460] memblock_alloc_internal+0x88/0x100 > [0.089532] memblock_alloc_try_nid+0x148/0x1ac > [0.089604] kfence_alloc_pool+0x44/0x6c > [0.089674] mm_init+0x28/0x98 > [0.089733] start_kernel+0x178/0x3e8 > [0.089797] __primary_switched+0xc4/0xcc > [0.090185] cblist_init_generic: Setting adjustable number of callback queues. > > > early_memtest reports no problems, > > > [0.000000] Zone ranges: > [0.000000] DMA [mem 0x0000000000000000-0x000000003fffffff] > [0.000000] DMA32[mem 0x0000000040000000-0x000000007fffffff] > [0.000000] Normal empty > [0.000000] Movable zone start for each node > [0.000000] Early memory node ranges > [0.000000] node 0: [mem 0x0000000000000000-0x0000000037ffffff] > [0.000000] node 0: [mem 0x0000000040000000-0x000000007fffffff] > [0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000007fffffff] > > > The Address differs a bit across reboots, but callstack looks always the same, and "Object is always 0xffffff806e24d000 (size 2097152)" > > > Aug 15 03:42:44 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 03:50:37 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 03:50:37 kernel:kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) > Aug 15 06:58:14 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 07:04:01 kernel:kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) > Aug 15 07:04:01 kernel:kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) > Aug 15 07:27:40 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 07:36:10 kernel:kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) > Aug 15 07:41:57 kernel:kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) > Aug 15 07:47:43 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 07:53:29 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 07:59:18 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 08:05:06 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 08:13:00 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 08:21:47 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 08:27:36 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 08:33:23 kernel:kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) > Aug 15 08:39:13 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 08:45:03 kernel:kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) > Aug 15 08:50:51 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 08:56:40 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 09:02:27 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 09:08:16 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 09:23:45 kernel:kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) > Aug 15 09:32:34 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 09:38:23 kernel:kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) > Aug 15 09:44:09 kernel:kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) > Aug 15 09:49:55 kernel:kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) > Aug 15 09:55:40 kernel:kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) > Aug 15 10:01:27 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 10:07:19 kernel:kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) > Aug 15 10:15:13 kernel:kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) > Aug 15 10:24:00 kernel:kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) > Aug 15 10:28:56 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 10:34:44 kernel:kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) > Aug 15 10:42:45 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 10:51:32 kernel:kmemleak: Cannot insert 0xffffff806e24ff40 into the object search tree (overlaps existing) > Aug 15 11:03:53 kernel:kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) > Aug 15 11:14:55 kernel:kmemleak: Cannot insert 0xffffff806e24f000 into the object search tree (overlaps existing) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel