[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240207181619.GDZcPI87_Bq0Z3ozUn@fat_crate.local>
Date: Wed, 7 Feb 2024 19:16:19 +0100
From: Borislav Petkov <bp@...en8.de>
To: Marco Elver <elver@...gle.com>
Cc: Matthieu Baerts <matttbe@...nel.org>,
Alexander Potapenko <glider@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>, kasan-dev@...glegroups.com,
Netdev <netdev@...r.kernel.org>, Jakub Kicinski <kuba@...nel.org>,
linux-hardening@...r.kernel.org, Kees Cook <keescook@...omium.org>,
the arch/x86 maintainers <x86@...nel.org>
Subject: Re: KFENCE: included in x86 defconfig?
On Wed, Feb 07, 2024 at 07:05:31PM +0100, Marco Elver wrote:
> I think this would belong into some "hardening" config - while KFENCE
> is not a mitigation (due to sampling) it has the performance
> characteristics of unintrusive hardening techniques, so I think it
> would be a good fit. I think that'd be
> "kernel/configs/hardening.config".
Instead of doing a special config for all the parties out there, why
don't parties simply automate their testing efforts by merging config
snippets into the default configs using
scripts/kconfig/merge_config.sh
before they run their specialized tests?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists