linux-kernel - Re: 32 bit qemu regression from v6.5 tip pull [6c480f222128 x86/alternative: Rewrite optimize

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: <e49abe2b336ce7534e9a7c82e21df9644f00f3a2.camel@linuxfoundation.org>
Date:   Wed, 22 Nov 2023 14:11:26 +0000
From:   Richard Purdie <richard.purdie@...uxfoundation.org>
To:     Linux regressions mailing list <regressions@...ts.linux.dev>,
        paul.gortmaker@...driver.com
Cc:     bp@...en8.de, linux-kernel@...r.kernel.org, peterz@...radead.org,
        tglx@...utronix.de, x86@...nel.org
Subject: Re: 32 bit qemu regression from v6.5 tip pull [6c480f222128
 x86/alternative: Rewrite optimize_nops() some]

On Sat, 2023-11-11 at 12:51 +0100, Linux regression tracking (Thorsten
Leemhuis) wrote:
> [CCing the regression list, as it should be in the loop for regressions:
> https://docs.kernel.org/admin-guide/reporting-regressions.html]
> 
> > [Re: 32 bit qemu regression from v6.5 tip pull [6c480f222128 x86/alternative: Rewrite optimize_nops() some]] On 30/10/2023 (Mon 20:30) Thomas Gleixner wrote:
> > 
> > > On Mon, Oct 30 2023 at 19:24, Thomas Gleixner wrote:
> > 
> > > > Can you add "debug-alternative" to the kernel command line and log both
> > > > a working and the non-working kernel output. It's noisy :)
> > > > 
> > > > Also do you have a .config and the qemu command line handy?
> > > 
> > > Forgot to ask: Does the probkem persist with 6.6 ?
> > 
> > My bad, should have mentioned v6.6 and linux-next is impacted. Always a
> > conflict between burying the lead and boring people with details.
> 
> Paul, was this regression ever solved? I wonder as I could not find
> anything with a "Fixes: 6c480f222128 [...]" tag on lore and this thread
> looks stalled.

I didn't see a reply to this. I can confirm the issue is still present
and we're not aware of any fix yet.

Cheers,

Richard