| 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
| ||
|
Message-id: <86cd47334b00b6aa9b5d0ebf389a6fe76f21c641.1312323131.git.len.brown@intel.com> Date: Tue, 02 Aug 2011 18:14:39 -0400 From: Len Brown <lenb@...nel.org> To: linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org Cc: Huang Ying <ying.huang@...el.com>, Len Brown <len.brown@...el.com> Subject: [PATCH 06/19] ACPI, APEI, GHES, Prevent GHES to be built as module From: Huang Ying <ying.huang@...el.com> GHES (Generic Hardware Error Source) is used to process hardware error notification in firmware first mode. But because firmware first mode can be turned on but can not be turned off, it is unreasonable to unload the GHES module with firmware first mode turned on. To avoid confusion, this patch makes GHES can be enabled/disabled in configuration time, but not built as module and unloaded at run time. Signed-off-by: Huang Ying <ying.huang@...el.com> Reviewed-by: Andi Kleen <ak@...ux.intel.com> Reviewed-by: Matthew Garrett <mjg@...hat.com> Signed-off-by: Len Brown <len.brown@...el.com> --- drivers/acpi/apei/Kconfig | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/acpi/apei/Kconfig b/drivers/acpi/apei/Kconfig index f739a70..3f45dde 100644 --- a/drivers/acpi/apei/Kconfig +++ b/drivers/acpi/apei/Kconfig @@ -10,7 +10,7 @@ config ACPI_APEI error injection. config ACPI_APEI_GHES - tristate "APEI Generic Hardware Error Source" + bool "APEI Generic Hardware Error Source" depends on ACPI_APEI && X86 select ACPI_HED help -- 1.7.6.396.ge0613 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists