linux-kernel - Re: [GIT PULL] perf events fix

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAHk-=wgdoAbw2zX6j+HGi+=ZmNKihA5rgpGfC925hq8o73zUEQ@mail.gmail.com>
Date: Sun, 1 Feb 2026 12:08:22 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org, 
	Arnaldo Carvalho de Melo <acme@...nel.org>, Jiri Olsa <jolsa@...nel.org>, 
	Alexander Shishkin <alexander.shishkin@...ux.intel.com>, Mark Rutland <mark.rutland@....com>, 
	Namhyung Kim <namhyung@...nel.org>
Subject: Re: [GIT PULL] perf events fix

On Sun, 1 Feb 2026 at 12:04, Peter Zijlstra <peterz@...radead.org> wrote:
>
> OK fair enough. Usually I'm fairly hesitant to rush things through
> /urgent

In general I very much applaud that, but late in the rc series, the
question then becomes "should it go into the final release at all?".

And if the answer is "yes", then earlier is better than just before the release.

Of course, potentially the answer is "better wait for next release and
maybe back-port", and then the question is one of "risk vs extra work
for the stable team".

IOW, right now I don't think "wait a few more days" is the answer either way.

           Linus