linux-kernel - Re: [PATCH v3 0/3] alpha: stack fixes

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: <alpine.DEB.2.21.2502081630030.65342@angie.orcam.me.uk>
Date: Sat, 8 Feb 2025 17:05:16 +0000 (GMT)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: Ivan Kokshaysky <ink@...een.parts>
cc: Richard Henderson <richard.henderson@...aro.org>, 
    Matt Turner <mattst88@...il.com>, Oleg Nesterov <oleg@...hat.com>, 
    Al Viro <viro@...iv.linux.org.uk>, Arnd Bergmann <arnd@...db.de>, 
    "Paul E. McKenney" <paulmck@...nel.org>, 
    Magnus Lindholm <linmag7@...il.com>, linux-alpha@...r.kernel.org, 
    linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH v3 0/3] alpha: stack fixes

On Tue, 4 Feb 2025, Ivan Kokshaysky wrote:

> This series fixes oopses on Alpha/SMP observed since kernel v6.9. [1]
> Thanks to Magnus Lindholm for identifying that remarkably longstanding
> bug.

 Thank you.  TL;DR: I've completed regression testing now and the results 
are looking good, so I have posted my Tested-by: tags now.

 Sadly original verification triggered a glitch which sometimes happens in 
the operation of my server's intranet network card that puts the device 
offline until it's hot-removed and the re-discovered.  I suspect a driver 
bug triggering under higher traffic, but that yet has to be investigated 
and it's a bit of a challenge with a machine that is at a remote location 
and in constant use.

 I have only discovered it once 1023 tests got affected and consequently 
failed due to the inability to reach the target Alpha system.  I concluded 
it was infeasible to run the failed tests by hand and then try to merge 
the results.

 Instead I disabled the extra prolonged tests discussed in the previous  
update and rerun the remaining whole testsuite.  That completed in ~23h 
and produced a few regressions and progressions, the former for the "math" 
and "nptl" test subsets, as well as one "string" test ("test-strnlen").  I 
have therefore verified them by hand and triggered the failures with your 
patchset removed, so I concluded their failed results are not the outcome 
of your changes.

 So this is good to go in as far as I'm concerned, as noted at the top.  
Thank you for taking time to work on this problem.

  Maciej