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: <CAJZ5v0jHOZ2TerHXnG6ZoLO1QbyxO1ACGFAiJBxTsJmhSZsd8Q@mail.gmail.com>
Date: Thu, 27 Nov 2025 13:55:06 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: "lihuisong (C)" <lihuisong@...wei.com>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>, ACPI Devel Maling List <linux-acpi@...r.kernel.org>, 
	Linux PM <linux-pm@...r.kernel.org>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, 
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [GIT PULL] Urgent ACPI support fix for v6.18

On Thu, Nov 27, 2025 at 3:09 AM lihuisong (C) <lihuisong@...wei.com> wrote:
>
> Hello Rafael,
>
> 在 2025/11/26 20:54, Rafael J. Wysocki 写道:
> > Hi Linus,
> >
> > Please pull from the tag
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
> >   acpi-6.18-rc8
> >
> > with top-most commit 43ff36c4a5a574ee83b4b0d3f3d74f09a3a8c2d3
> >
> >   Revert "ACPI: processor: idle: Optimize ACPI idle driver registration"
> >
> > on top of commit ac3fd01e4c1efce8f2c054cdeb2ddd2fc0fb150d
> >
> >   Linux 6.18-rc7
> >
> > to receive an urgent ACPI support fix for 6.18.
> >
> > This reverts a commit that attempted to make the code in the ACPI
> > processor driver more straightforward, but it turned out to cause
> > the kernel to crash on at least one system, along with some further
> > cleanups on top of it.
> I just found that "ACPI: processor: idle: Optimize ACPI idle driver
> registration" depends on the change
> about cpuhp_setup_state in the commit [1]. Or many CPUs don't create
> cpuidle directory.
> What is the crash? Do you have releated trace?

Yes, please see

https://lore.kernel.org/lkml/20251124200019.GIaSS5U9HhsWBotrQZ@fat_crate.local/

(from the Closes: tag in the revert commit).

Thanks!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ