From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Jan Engelhardt <jengelh@inai.de>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] x86: ignore unspecified bit positions in the ACPI global lock field
Date: Sat, 14 Mar 2020 10:46:00 +0100 [thread overview]
Message-ID: <2030043.rEjxodZhqh@kreacher> (raw)
In-Reply-To: <20200305122425.32223-1-jengelh@inai.de>
On Thursday, March 5, 2020 1:24:25 PM CET Jan Engelhardt wrote:
> The value in "new" is constructed from "old" such that all bits defined
> as reserved by the ACPI spec[1] are left untouched. But if those bits
> do not happen to be all zero, "new < 3" will not evaluate to true.
>
> The firmware of the laptop(s) Medion MD63490 / Akoya P15648 comes with
> garbage inside the "FACS" ACPI table. The starting value is
> old=0x4944454d, therefore new=0x4944454e, which is >= 3. Mask off
> the reserved bits.
>
> [1] https://uefi.org/sites/default/files/resources/ACPI_6_2.pdf
>
> References: https://bugzilla.kernel.org/show_bug.cgi?id=206553
> Signed-off-by: Jan Engelhardt <jengelh@inai.de>
> ---
> arch/x86/kernel/acpi/boot.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/kernel/acpi/boot.c b/arch/x86/kernel/acpi/boot.c
> index 04205ce127a1..f9e84a0e2fa2 100644
> --- a/arch/x86/kernel/acpi/boot.c
> +++ b/arch/x86/kernel/acpi/boot.c
> @@ -1740,7 +1740,7 @@ int __acpi_acquire_global_lock(unsigned int *lock)
> new = (((old & ~0x3) + 2) + ((old >> 1) & 0x1));
> val = cmpxchg(lock, old, new);
> } while (unlikely (val != old));
> - return (new < 3) ? -1 : 0;
> + return ((new & 0x3) < 3) ? -1 : 0;
> }
>
> int __acpi_release_global_lock(unsigned int *lock)
>
Applied as 5.7 material, thanks!
next prev parent reply other threads:[~2020-03-15 1:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 12:24 [PATCH] x86: ignore unspecified bit positions in the ACPI global lock field Jan Engelhardt
2020-03-14 9:46 ` Rafael J. Wysocki [this message]
2020-03-19 10:46 ` Jan Engelhardt
2020-03-19 12:22 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2030043.rEjxodZhqh@kreacher \
--to=rjw@rjwysocki.net \
--cc=jengelh@inai.de \
--cc=linux-acpi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox