From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: Aaron Tomlin <atomlin@atomlin.com>,
oleg@redhat.com, akpm@linux-foundation.org,
gregkh@linuxfoundation.org, brauner@kernel.org, mingo@kernel.org
Cc: sean@ashe.io, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs/proc: Expose mm_cpumask in /proc/[pid]/status
Date: Thu, 18 Dec 2025 09:30:53 +0100 [thread overview]
Message-ID: <060edde3-7cc4-4a36-b9aa-824e607d954c@kernel.org> (raw)
In-Reply-To: <20251217024603.1846651-1-atomlin@atomlin.com>
On 12/17/25 03:46, Aaron Tomlin wrote:
> This patch introduces two new fields to /proc/[pid]/status to display the
> set of CPUs, representing the CPU affinity of the process's active
> memory context, in both mask and list format: "Cpus_active_mm" and
> "Cpus_active_mm_list". The mm_cpumask is primarily used for TLB and
> cache synchronisation.
>
> Exposing this information allows userspace to easily identify
> memory-task affinity, insight to NUMA alignment, CPU isolation and
> real-time workload placement.
>
> Frequent mm_cpumask changes may indicate instability in placement
> policies or excessive task migration overhead.
I agree with Oleg's comments.
Given that everybody has read access to /proc/$PID/status IIUC, I wonder
if that information could somehow help an attacker to better attack a
target program (knowing which CPUs have dirty TLB etc). As you saise,
it's primarily for TLB and cache sync ...
Just a thought, have nothing concrete in mind.
--
Cheers
David
next prev parent reply other threads:[~2025-12-18 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 2:46 [PATCH] fs/proc: Expose mm_cpumask in /proc/[pid]/status Aaron Tomlin
2025-12-17 17:33 ` Oleg Nesterov
2025-12-19 1:25 ` Aaron Tomlin
2025-12-18 8:30 ` David Hildenbrand (Red Hat) [this message]
2025-12-19 2:06 ` Aaron Tomlin
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=060edde3-7cc4-4a36-b9aa-824e607d954c@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=atomlin@atomlin.com \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=sean@ashe.io \
/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