[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z96qQm6qqRRcSL9j@gmail.com>
Date: Sat, 22 Mar 2025 13:17:06 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Ravi Bangoria <ravi.bangoria@....com>
Cc: peterz@...radead.org, namhyung@...nel.org, mingo@...hat.com,
acme@...nel.org, kan.liang@...ux.intel.com, mark.rutland@....com,
alexander.shishkin@...ux.intel.com, linux-kernel@...r.kernel.org,
matteorizzo@...gle.com, linux-perf-users@...r.kernel.org,
santosh.shukla@....com, ananth.narayan@....com,
sandipan.das@....com
Subject: Re: [PATCH v3 tip:perf/core] perf/amd/ibs: Prevent leaking sensitive
data to userspace
* Ravi Bangoria <ravi.bangoria@....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
Powered by blists - more mailing lists