From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from stravinsky.debian.org (stravinsky.debian.org [82.195.75.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AD2713BB9F3 for ; Fri, 3 Jul 2026 10:23:07 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=82.195.75.108 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783074189; cv=none; b=HvmmRIlvRACqi3Wmlm/oZZgWyHXwdCUDMMWPDeTEasnsI/ZXe89wTV1km3XG97Er8sfnHDdOW5q9/5JbSAd7K3x+HpkOYRZxghx2EPuGR1ddUnEXqqbVUY7l7rQho96SxLMk4ZazVT8/TlNL/CLU0t6//2Ko4MV85/C5OMpks8o= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783074189; c=relaxed/simple; bh=y1CHNhXW1g9dAY4apwJ7l+1myjFZ1I+t2uGgcQxW9eM=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=ZcISiVSmjy3DrKaTvZS7S4eRFgXTi4vN9apxfTRtyxTU+ZSBJPCReEpSH5/VEOERFU4hRAZP64ZxiIx4CdWeIABsym3QJXUVQ2uelIKGPOOV0hJ+Ha7vTg64L3PnD2vUY52P0QfWqD2jmqabDvnJF+H4kFSz233Mx8knX4TMQME= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=debian.org; spf=pass smtp.mailfrom=debian.org; dkim=pass (2048-bit key) header.d=debian.org header.i=@debian.org header.b=g2dOUQz7; arc=none smtp.client-ip=82.195.75.108 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=debian.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=debian.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=debian.org header.i=@debian.org header.b="g2dOUQz7" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; s=smtpauto.stravinsky; h=X-Debian-User:In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=BqWgzwoybqnURjD5nY9o5kxidm2izbLe4G4WC3Shb2E=; b=g2dOUQz7q7mvm1QKSnaopKuS7S dNLdDY7CwWPCaAP3l3xmVjyiXuFA+6dF6nBDFdYj+QweCilYUPl2B2EAxHeb3b3HRSrFvf8vhWJAS /gekcnMO/jVDoSnxPOWbICTmrO+fC4Ja/IRWDH6g+EjQ/uZeUJQD3eon3scS+JIZJBEZC2yNlo/Ph x9CrtCRGfyTyKzZCzpqkJu6bonSLp4r/OQfPDWWfw/ZG+XV7RfuqqXnqP0YjwEIfXY+/mWpAwbwyQ kwkyzS8v7lFs+o9h+49JreF8JGkAcYSoA7sfUwqPfQMv7kcW2VIlpOlkChYTyjdEn8e5LJf9c4auH ujS29gpg==; Received: from authenticated-user by stravinsky.debian.org with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from ) id 1wfb2k-009KgO-2x; Fri, 03 Jul 2026 10:22:47 +0000 Date: Fri, 3 Jul 2026 03:22:40 -0700 From: Breno Leitao To: Andrea Righi Cc: Ingo Molnar , Peter Zijlstra , Juri Lelli , Vincent Guittot , Dietmar Eggemann , Steven Rostedt , Ben Segall , Mel Gorman , Valentin Schneider , K Prateek Nayak , Christian Loehle , Phil Auld , Koba Ko , Felix Abecassis , Balbir Singh , Joel Fernandes , Shrikanth Hegde , linux-kernel@vger.kernel.org Subject: kmemleak: sched_domain_shared leaked on asymmetric-capacity + SCHED_CACHE Message-ID: References: <20260509180955.1840064-1-arighi@nvidia.com> <20260509180955.1840064-3-arighi@nvidia.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260509180955.1840064-3-arighi@nvidia.com> X-Debian-User: leitao Hi, On current linux-next (CONFIG_SCHED_CACHE=y) we hit a kmemleak on an arm64 box with asymmetric CPU capacity, triggered by a cpuset-driven sched-domain rebuild: kmemleak: unreferenced object 0xffff000100c95e80 (size 32): comm "kworker/22:1", pid 407, jiffies 4294669077 hex dump (first 32 bytes): 48 00 00 00 48 00 00 00 00 00 00 00 20 00 00 00 H...H....... ... backtrace (crc ec5d7053): __kmalloc_cache_node_noprof build_sched_domains partition_sched_domains rebuild_sched_domains_locked rebuild_sched_domains process_scheduled_works kthread ret_from_fork kmemleak: 1 new suspected memory leaks The leaked object is a struct sched_domain_shared (32 bytes with CONFIG_SCHED_CACHE) allocated in __sds_alloc(), inlined into build_sched_domains() Is this a known issue? --breno