[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgPwhqr7mwmXDzYkfAcMRu3zyKRxz3hh-wfg-BQxj+UZg@mail.gmail.com>
Date: Sat, 21 Jun 2025 08:35:28 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] ACPI fix for v6.16-rc3
On Sat, 21 Jun 2025 at 04:31, Rafael J. Wysocki <rafael@...nel.org> wrote:
>
> This fixes a crash in ACPICA while attempting to evaluate a control
> method that expects more arguments than are being passed to it, which
> was exposed by a defective firmware update from a prominent OEM on
> multiple systems.
Christ. Reading the ACPI issues page makes me go "D'oh".
Does anybody know what the heck Windows does in this situation? Does
it just happen to work because it uses random arguments and happily
dereferences bogus things without realizing, or does it do the "zero
out missing arguments" thing?
Because clearly that firmware bug must have passed entirely unnoticed
by people testing that thing on Windows...
Linus
Powered by blists - more mailing lists