linux-kernel - Re: Bug#1103397: linux-image-amd64: Kernel Panic: copy_fpstate_to

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

Message-ID: <aB0Q8S47iNeD1GOM@eldamar.lan>
Date: Thu, 8 May 2025 22:15:45 +0200
From: Salvatore Bonaccorso <carnil@...ian.org>
To: Larry Wei <larryw3i@...h.net>, 1103397@...s.debian.org
Cc: Ben Hutchings <ben@...adent.org.uk>, TonyWWang-oc@...oxin.com,
	"Chang S. Bae" <chang.seok.bae@...el.com>,
	Lyle Li <LyleLi@...oxin.com>, tglx@...utronix.de, mingo@...hat.com,
	bp@...en8.de, dave.hansen@...ux.intel.com, x86@...nel.org,
	hpa@...or.com, aruna.ramakrishna@...cle.com, pbonzini@...hat.com,
	levymitchell0@...il.com, attofari@...zon.de,
	linux-kernel@...r.kernel.org, CobeChen@...oxin.com,
	TimGuo@...oxin.com, LeoLiu-oc@...oxin.com
Subject: Re: Bug#1103397: linux-image-amd64: Kernel Panic:
  copy_fpstate_to_sigframe crashes.

Hi Larry Wei, hi Ben,

For context this is about https://bugs.debian.org/1103397, and which
Ben did forward in
https://lore.kernel.org/regressions/dddb6b8d56e3f28b914e1e243f948457d53149ce.camel@decadent.org.uk/T/

On Thu, May 08, 2025 at 03:12:31AM +0800, Larry Wei wrote:
> Thank you all,
> 
> I have pulled the newest `linux-next` changes and compiled it, my laptop
> boots well now! https://linux-hardware.org/?probe=271fabb7a4 , but it still
> prints some `WARNING` information at startup:
> https://linux-hardware.org/?probe=271fabb7a4&log=dmesg . May this output is
> useful for you maintainers.
> 
> And, thank you all again.

Going thorough the bugs I notice there was a related upstream
discussion/patch relating to ae6012d72fa6 ("x86/pkeys: Ensure updated
PKRU value is XRSTOR'd")  in the following:

https://lore.kernel.org/all/20250102075419.2559-1-TonyWWang-oc@zhaoxin.com/

There were some followups, but discussion ended on 18.01.2025.

Did this felt through the cracks?

Regards,
Salvatore