From: Ingo Molnar <mingo@kernel.org>
To: Ravi Bangoria <ravi.bangoria@amd.com>
Cc: peterz@infradead.org, namhyung@kernel.org, mingo@redhat.com,
acme@kernel.org, kan.liang@linux.intel.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, linux-kernel@vger.kernel.org,
matteorizzo@google.com, linux-perf-users@vger.kernel.org,
santosh.shukla@amd.com, ananth.narayan@amd.com,
sandipan.das@amd.com
Subject: Re: [PATCH v3 tip:perf/core] perf/amd/ibs: Prevent leaking sensitive data to userspace
Date: Sat, 22 Mar 2025 13:17:06 +0100 [thread overview]
Message-ID: <Z96qQm6qqRRcSL9j@gmail.com> (raw)
In-Reply-To: <7c9a00c3-b2a0-4f8a-945b-cc90e492988a@amd.com>
* Ravi Bangoria <ravi.bangoria@amd.com> wrote:
> > How well was this tested? v6.14 will be released tomorrow most
> > likely, so it's a bit risky to apply such a large patch so late.
> > Applying the -v1 fix was a bit risky already.
>
> I understand. Although I've done a fair bit of testing and ran perf-
> fuzzer for few hours before posting,
That's reassuring!
> I'm also not in favor of rushing. I think it's safe to defer it to
> 6.15.
I'm leaning towards sending the fix to Linus later today, because the
leak has been introduced in this merge window AFAICS, via d29e744c7167,
and I'd prefer us not releasing a buggy kernel ...
Thanks,
Ingo
next prev parent reply other threads:[~2025-03-22 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 16:12 [PATCH v3 tip:perf/core] perf/amd/ibs: Prevent leaking sensitive data to userspace Ravi Bangoria
2025-03-22 7:24 ` Ingo Molnar
2025-03-22 10:15 ` Ravi Bangoria
2025-03-22 12:17 ` Ingo Molnar [this message]
2025-03-22 15:39 ` Ravi Bangoria
2025-03-23 4:22 ` Namhyung Kim
2025-03-22 7:30 ` [tip: perf/urgent] " tip-bot2 for Namhyung Kim
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=Z96qQm6qqRRcSL9j@gmail.com \
--to=mingo@kernel.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ananth.narayan@amd.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matteorizzo@google.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.com \
--cc=sandipan.das@amd.com \
--cc=santosh.shukla@amd.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;
as well as URLs for NNTP newsgroup(s).