linux-kernel - Re: [PATCH] selftests/futex: Fix futex_numa

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <64deb0ae-5641-4ceb-889e-0ef1087175fb@igalia.com>
Date: Mon, 1 Sep 2025 09:49:14 -0300
From: André Almeida <andrealmeid@...lia.com>
To: Borislav Petkov <bp@...en8.de>,
 Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: Waiman Long <llong@...hat.com>, Darren Hart <dvhart@...radead.org>,
 Davidlohr Bueso <dave@...olabs.net>, Ingo Molnar <mingo@...hat.com>,
 Juri Lelli <juri.lelli@...hat.com>, Peter Zijlstra <peterz@...radead.org>,
 Thomas Gleixner <tglx@...utronix.de>,
 Valentin Schneider <vschneid@...hat.com>, kernel-dev@...lia.com,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] selftests/futex: Fix futex_numa_mpol's memory out of
 range subtest

Em 29/08/2025 07:07, Borislav Petkov escreveu:
> On Fri, Aug 29, 2025 at 08:16:24AM +0200, Sebastian Andrzej Siewior wrote:
>>> No objections merging Waiman fix first, but we are still in -rc3, so maybe
>>> there's time for the rework in this cycle?
> 
> ... and you can rework all you want. When your solution is ready and everyone
> agrees, there's nothing wrong with queueing it ontop or delaying it for the
> next merge window.
> 
>> On the regression list, we this one fallout in the testsuite. I would
>> like to get an easy fix for -rc4 and be done with it for this cycle.
> 
> There's absolutely no place for hurrying things, especially for self tests. So
> take your time pls.
> 

Sure, I don't want to hurry things, I'm just trying to understand better 
the rationale of having this for the next cycle, and if I would have to 
wait or not till the next kernel release to send the patch :)