linux-kernel - Re: [PATCH 1/2] arm64/acpi: panic when failed to init acpi table with acpi=force option

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

Message-ID: <4c8e92ac-1e16-4d0f-8710-96a167d75d97@sirena.org.uk>
Date: Mon, 25 Nov 2024 15:48:44 +0000
From: Mark Brown <broonie@...nel.org>
To: Yeoreum Yun <yeoreum.yun@....com>
Cc: catalin.marinas@....com, will@...nel.org, sudeep.holla@....com,
	guohanjun@...wei.com, gshan@...hat.com, prarit@...hat.com,
	Jonathan.Cameron@...wei.com, dwmw@...zon.co.uk, ardb@...nel.org,
	hagarhem@...zon.com, linux-arm-kernel@...ts.infradead.org,
	linux-efi@...r.kernel.org, linux-kernel@...r.kernel.org, nd@....com
Subject: Re: [PATCH 1/2] arm64/acpi: panic when failed to init acpi table
 with acpi=force option

On Mon, Nov 25, 2024 at 02:58:47PM +0000, Yeoreum Yun wrote:

> when the acpi=force option is used,
> the system does not fall back to the device tree (DT).
> If it fails to initialize the ACPI table, it cannot proceed further.
> In such cases, the system should invoke panic() to avoid contradicting
> the user's explicit intent, as failing or
> proceeding with unintended behavior would violate their wishes.

This makes sense to me:

Reviewed-by: Mark Brown <broonie@...nel.org>

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)