From: Dominik Maier <dmnk@google.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
linux-kernel@vger.kernel.org, dmnk+artist@google.com,
Dominik Maier <dmnk@google.com>
Subject: Re: [PATCH] sched/mmcid: fix per-CPU CID ownership leak in sched_mm_cid_exit()
Date: Thu, 19 Nov 2026 20:23:06 +0100 [thread overview]
Message-ID: <20261119192306.reply-tglx-sched-mmcid@google.com> (raw)
In-Reply-To: <87cxsfwkm7.ffs@fw13>
Hi Thomas,
Thank you for taking a look on November 8 and for pointing us to your
broader rework at:
https://lore.kernel.org/all/87mrs8bhp4.ffs@fw13
Apologies as well for the two process mistakes in our original
submission: omitting linux-kernel@vger.kernel.org from Cc, and including
the removed Assisted-by: tag instead of describing the tooling and
validation in plain English in the changelog. We have corrected our
workflow on both counts.
Re-initializing the MM CID state explicitly across execve() rather than
relying on the last-user exit path in sched_mm_cid_exit() is much
cleaner. We will test your explicit exec re-initialization approach
against our reproducer in QEMU/KVM and follow up directly on that thread
with test results.
Best regards,
Dominik
parent reply other threads:[~2026-11-19 19:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87cxsfwkm7.ffs@fw13>]
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=20261119192306.reply-tglx-sched-mmcid@google.com \
--to=dmnk@google.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=dmnk+artist@google.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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
all inboxes | Powered by JetHome®