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: <a688793b-f7e8-18a4-3eb2-877f1522d8f3@kernel.org>
Date:   Tue, 16 Jul 2019 00:13:23 -0400
From:   Sinan Kaya <Okaya@...nel.org>
To:     Sasha Levin <sashal@...nel.org>, marc.zyngier@....com,
        will.deacon@....com, julien.thierry@....com,
        catalin.marinas@....com
Cc:     linux-kernel@...r.kernel.org, linux-kernel@...rosoft.com,
        linux-acpi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        stable@...nel.org
Subject: Re: [PATCH] ARM64/irqchip: Make ACPI_IORT depend on PCI again

On 7/16/2019 12:04 AM, Sasha Levin wrote:
> ACPI_IORT lost it's explicit dependency on PCI in c6bb8f89fa6df
> ("ARM64/irqchip: Update ACPI_IORT symbol selection logic") where the
> author has relied on the general dependency of ACPI on PCI.
> 
> However, that dependency was finally removed in 5d32a66541c4 ("PCI/ACPI:
> Allow ACPI to be built without CONFIG_PCI set") and now ACPI_IORT breaks
> when we try and build it without PCI support.
> 
> This patch brings back the explicit dependency of ACPI_IORT on PCI.
> 
> Fixes: 5d32a66541c4 ("PCI/ACPI: Allow ACPI to be built without CONFIG_PCI set")
> Cc: stable@...nel.org
> Signed-off-by: Sasha Levin <sashal@...nel.org>

Do you have more detail on what really is broken without this patch?

It should be possible to build IORT table without PCI.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ