From: Shakeel Butt <shakeel.butt@linux.dev>
To: Suren Baghdasaryan <surenb@google.com>
Cc: akpm@linux-foundation.org, kent.overstreet@linux.dev,
vbabka@suse.cz, mhocko@suse.com, jackmanb@google.com,
hannes@cmpxchg.org, ziy@nvidia.com, usamaarif642@gmail.com,
00107082@163.com, pasha.tatashin@soleen.com,
souravpanda@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] alloc_tag: prevent enabling memory profiling if it was shut down
Date: Tue, 9 Sep 2025 22:32:15 -0700 [thread overview]
Message-ID: <k6dhapofhcrhmcigqasy25lxmht4ybxp7jv5rg5oe4fjt3feop@lkyiqad43b5b> (raw)
In-Reply-To: <20250909233409.1013367-3-surenb@google.com>
On Tue, Sep 09, 2025 at 04:34:08PM -0700, Suren Baghdasaryan wrote:
> Memory profiling can be shut down due to reasons like a failure during
> initialization. When this happens, the user should not be able to
> re-enable it. Current sysctrl interface does not handle this properly
> and will allow re-enabling memory profiling. Fix this by checking for
> this condition during sysctrl write operation.
>
> Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Acked-by: Shakeel Butt <shakeel.butt@linux.dev>
next prev parent reply other threads:[~2025-09-10 5:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 23:34 [PATCH 0/3] Minor fixes for memory allocation profiling Suren Baghdasaryan
2025-09-09 23:34 ` [PATCH 1/3] alloc_tag: use release_pages() in the cleanup path Suren Baghdasaryan
2025-09-10 5:31 ` Shakeel Butt
2025-09-10 20:49 ` Usama Arif
2025-09-12 21:05 ` Suren Baghdasaryan
2025-09-09 23:34 ` [PATCH 2/3] alloc_tag: prevent enabling memory profiling if it was shut down Suren Baghdasaryan
2025-09-10 5:32 ` Shakeel Butt [this message]
2025-09-10 20:51 ` Usama Arif
2025-09-11 17:01 ` Suren Baghdasaryan
2025-09-09 23:34 ` [PATCH 3/3] alloc_tag: avoid warnings when freeing non-compound "tail" pages Suren Baghdasaryan
2025-09-11 20:01 ` Shakeel Butt
2025-09-11 20:12 ` Suren Baghdasaryan
2025-09-11 21:44 ` Shakeel Butt
2025-09-11 21:51 ` Suren Baghdasaryan
2025-09-11 22:58 ` Shakeel Butt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=k6dhapofhcrhmcigqasy25lxmht4ybxp7jv5rg5oe4fjt3feop@lkyiqad43b5b \
--to=shakeel.butt@linux.dev \
--cc=00107082@163.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=pasha.tatashin@soleen.com \
--cc=souravpanda@google.com \
--cc=surenb@google.com \
--cc=usamaarif642@gmail.com \
--cc=vbabka@suse.cz \
--cc=ziy@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox