From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: [PATCH 16/21] linux: Disable ACPI configfs support Date: Tue, 27 Dec 2022 12:29:22 +0100 Message-ID: In-Reply-To: <7897a29a-1dae-0158-f207-f67a3d91ae16@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1029105309070818631==" List-Id: --===============1029105309070818631== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Acked-by: Michael Tremer > On 26 Dec 2022, at 20:29, Peter M=C3=BCller wr= ote: >=20 > 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. >=20 > Signed-off-by: Peter M=C3=BCller > --- > config/kernel/kernel.config.x86_64-ipfire | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) >=20 > diff --git a/config/kernel/kernel.config.x86_64-ipfire b/config/kernel/kern= el.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 --===============1029105309070818631==--