[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20260116124549.db884e094f093340c63aafbc@linux-foundation.org>
Date: Fri, 16 Jan 2026 12:45:49 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Suren Baghdasaryan <surenb@...gle.com>
Cc: kent.overstreet@...ux.dev, corbet@....net, willy@...radead.org,
sj@...nel.org, ranxiaokai627@....com, ran.xiaokai@....com.cn,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, stable@...r.kernel.org
Subject: Re: [PATCH v2 1/1] Docs/mm/allocation-profiling: describe sysctrl
limitations in debug mode
On Fri, 16 Jan 2026 10:44:23 -0800 Suren Baghdasaryan <surenb@...gle.com> wrote:
> When CONFIG_MEM_ALLOC_PROFILING_DEBUG=y, /proc/sys/vm/mem_profiling is
> read-only to avoid debug warnings in a scenario when an allocation is
> made while profiling is disabled (allocation does not get an allocation
> tag), then profiling gets enabled and allocation gets freed (warning due
> to the allocation missing allocation tag).
Cool, thanks.
> Cc: stable@...r.kernel.org
Documentation/process/stable-kernel-rules.rst tells me that -stable tree
users prefer incorrect documentation ;)
Powered by blists - more mailing lists