From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 E34BC45BE3 for ; Tue, 24 Mar 2026 00:49:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774313371; cv=none; b=V8QoxZhm8v9rpHo7AzjQW/TubJ4CxLphibZ+r/IFUhJXNNoeyZ5I7UI8p5wdWU6VqX2aYm3GJYJtRJDSgAnj709WKnnpwd21TAht/yy1XtfvQNgDwUkgJUDyFSN4gp5W6fWxsKe+776xaQnc7K1hnjZtfJl2DRbEKKQjAs75HsM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774313371; c=relaxed/simple; bh=ZaXWNyOg2XPWmXfa+V0XWwnXp4bXe0r1OTT8sXXPW1w=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=jaxUfCA3HsGqind20myzo3Qd1djx11h3KIlN1JX2D8dFRdWl4J0yrVef+rOUoJmAuqV4i4e4N0rVSpkEwlky5I1RyF0ARyIVSfN4iMS5vyuBNUnc5LYUB95xi5wbkiPgrpkZVCxA9Pl5E6KeWpDq7ZT81i4BAUrjsNIVTE5kU1o= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=ldj034ey; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="ldj034ey" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2F1F2C4CEF7; Tue, 24 Mar 2026 00:49:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1774313370; bh=ZaXWNyOg2XPWmXfa+V0XWwnXp4bXe0r1OTT8sXXPW1w=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=ldj034ey75XF5zOvdPKcpjcNxXPmm9zzSrHMHntBi10cgrtdYQA5Spk6IA1E3H45N Kf/PLsmdo8wLOfUlrbF1epFNV57w3M//OJKcdGCsl+4V7PXUorwTTpxLZEJJQBEUbJ YzhY/QDY/43ii0ojQz/VOLf/UXYxgPRB+Oi2mnHIlJW0y5PnJG9pxnpR6NdoC2sJFo Uj7apBzIcas64FVxEiYn7ke4yoItkE8z9PgQzwardsuBfAi/6J/seDwhpXbWvC90MO 2d/B+O/Gc0cuMhvg+jgc7AcnEcz6+6CyfSRSbBeIkec4ypOSe8E44wF6TerGWpHhgp UzaIn9whoffhw== From: SeongJae Park To: Breno Leitao Cc: SeongJae Park , Andrew Morton , Catalin Marinas , David Hildenbrand , Lorenzo Stoakes , "Liam R. Howlett" , Vlastimil Babka , Mike Rapoport , Suren Baghdasaryan , Michal Hocko , linux-mm@kvack.org, linux-kernel@vger.kernel.org, kernel-team@meta.com Subject: Re: [PATCH] mm: kmemleak: add CONFIG_DEBUG_KMEMLEAK_VERBOSE build option Date: Mon, 23 Mar 2026 17:49:22 -0700 Message-ID: <20260324004923.87190-1-sj@kernel.org> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260323-kmemleak_report-v1-1-ba2cdd9c11b9@debian.org> References: Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit On Mon, 23 Mar 2026 04:12:13 -0700 Breno Leitao wrote: > Add a Kconfig option to default kmemleak verbose mode on at build time. > This option depends on DEBUG_KMEMLEAK_AUTO_SCAN since verbose reporting > is only meaningful when the automatic scanning thread is running. > > When enabled, kmemleak prints full details (backtrace, hex dump, address) > of unreferenced objects to dmesg as they are detected during scanning, > removing the need to manually read /sys/kernel/debug/kmemleak. > > Making this a compile-time option rather than a boot parameter allows > debug kernel flavors to enable verbose kmemleak reporting by default > without requiring changes to boot arguments. A machine can simply swap > to a debug kernel and benefit from kmemleak reporting automatically. > > By surfacing leak reports directly in dmesg, they are automatically > forwarded through any kernel logging infrastructure and can be easily > captured by log aggregation tooling, making it practical to monitor > memory leaks across large fleets. > > The verbose setting can still be toggled at runtime via > /sys/module/kmemleak/parameters/verbose. > > Signed-off-by: Breno Leitao Acked-by: SeongJae Park Thanks, SJ [...]