linux-kernel - Re: New kernel warning after updating from LTS 5.15.110 to 5.15.112 (and 5.15.113)

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: <1f8fae1e-5610-1ce1-6db6-a57f4152c9d7@kunbus.com>
Date:   Wed, 7 Jun 2023 17:01:37 +0200
From:   Lino Sanfilippo <l.sanfilippo@...bus.com>
To:     Chris Packham <Chris.Packham@...iedtelesis.co.nz>,
        Bagas Sanjaya <bagasdotme@...il.com>,
        Jarkko Sakkinen <jarkko@...nel.org>,
        Sasha Levin <sashal@...nel.org>,
        Peter Huewe <peterhuewe@....de>, Jason Gunthorpe <jgg@...pe.ca>
Cc:     Linux Kernel Integrity <linux-integrity@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Regressions <regressions@...ts.linux.dev>,
        Lukas Wunner <lukas@...ner.de>,
        Philipp Rosenberger <p.rosenberger@...bus.com>
Subject: Re: New kernel warning after updating from LTS 5.15.110 to 5.15.112
 (and 5.15.113)

Hi Chris,

On 07.06.23 05:23, Chris Packham wrote:


>> Chris, could you test again with commit 0c7e66e5fd69 additionally applied and confirm that the warning is gone?
> 
> Yes with 0c7e66e5fd69 cherry-picked on top the warning goes away. Adding
> e644b2f498d2 doesn't seem to change anything (still reports that
> interrupts aren't working) but that's the same as the latest mainline on
> this hardware.


Thanks a lot for testing this!

If interrupts do not even work with the latest mainline kernel something
else must be wrong.

But it is good to know that the cherry-pick fixes at least the regression.


Best regards,
Lino