From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: [PATCH 16/21] linux: Disable ACPI configfs support Date: Mon, 26 Dec 2022 19:29:51 +0000 Message-ID: <7897a29a-1dae-0158-f207-f67a3d91ae16@ipfire.org> In-Reply-To: <0e60a1de-6210-835e-54a4-ec5e3128e42e@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5522643254928151258==" List-Id: --===============5522643254928151258== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable This is disabled in IPFire 3.x, and projects such as grsecurity recommend doing so for security reasons as well. Also, skimming through our source code, there is no point where this ACPI configfs would have been explicitly mounted, which leads to the assumption that we never used it anyway. Signed-off-by: Peter M=C3=BCller --- config/kernel/kernel.config.x86_64-ipfire | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/kernel/kernel.config.x86_64-ipfire b/config/kernel/kernel= .config.x86_64-ipfire index 763c7c842..5a8a9e14b 100644 --- a/config/kernel/kernel.config.x86_64-ipfire +++ b/config/kernel/kernel.config.x86_64-ipfire @@ -552,7 +552,7 @@ CONFIG_ACPI_APEI_MEMORY_FAILURE=3Dy CONFIG_ACPI_WATCHDOG=3Dy CONFIG_ACPI_EXTLOG=3Dm CONFIG_ACPI_ADXL=3Dy -CONFIG_ACPI_CONFIGFS=3Dm +# CONFIG_ACPI_CONFIGFS is not set CONFIG_PMIC_OPREGION=3Dy # CONFIG_XPOWER_PMIC_OPREGION is not set CONFIG_ACPI_VIOT=3Dy --=20 2.35.3 --===============5522643254928151258==--