linux-kernel - Re: [PATCH 6.12 000/172] 6.12.6-rc1 review

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: <60f5d471-7c5c-4a1f-a1de-c52e272ca852@roeck-us.net>
Date: Wed, 18 Dec 2024 21:56:56 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Jiri Slaby <jirislaby@...nel.org>, Peter Zijlstra <peterz@...radead.org>
Cc: Naresh Kamboju <naresh.kamboju@...aro.org>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>, stable@...r.kernel.org,
 patches@...ts.linux.dev, linux-kernel@...r.kernel.org,
 torvalds@...ux-foundation.org, akpm@...ux-foundation.org, shuah@...nel.org,
 patches@...nelci.org, lkft-triage@...ts.linaro.org, pavel@...x.de,
 jonathanh@...dia.com, f.fainelli@...il.com, sudipm.mukherjee@...il.com,
 srw@...dewatkins.net, rwarsow@....de, conor@...nel.org,
 hargar@...rosoft.com, broonie@...nel.org, Juergen Gross <jgross@...e.com>,
 Josh Poimboeuf <jpoimboe@...hat.com>,
 Dan Carpenter <dan.carpenter@...aro.org>, Arnd Bergmann <arnd@...db.de>,
 Anders Roxell <anders.roxell@...aro.org>
Subject: Re: [PATCH 6.12 000/172] 6.12.6-rc1 review

On 12/18/24 09:48, Jiri Slaby wrote:
> On 18. 12. 24, 17:54, Peter Zijlstra wrote:
>> On Wed, Dec 18, 2024 at 08:53:39AM -0800, Guenter Roeck wrote:
>>
>>> The fix is not yet in mainline, meaning the offending patch now results
>>> in the same build failure there.
> 
> Yes, as I wrote in the aforementioned message :).
> 
>> It's a test, to see if anybody except the build robots actually gives a
>> damn about i386 :-)
> 
> This is not much of a robot -- openSUSE still provides 386. As a port now. I failed to destroy that port in past several attempts :P -- there were still users.
> 

For my part, if I get a few more of the "nobody except the build robots
actually gives a damn" or "why are you testing this or "you should not
be testing this" responses, I _will_ stop testing this and any other
configuration where people make such statements. I am getting tired of it.
If anyone doesn't want something tested, it should be dropped from the
kernel or at least be marked broken or disabled for build tests.

Guenter