From: Matthieu Baerts <matttbe@kernel.org>
To: Borislav Petkov <bp@alien8.de>, Marco Elver <elver@google.com>
Cc: Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
kasan-dev@googlegroups.com, Netdev <netdev@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
linux-hardening@vger.kernel.org,
Kees Cook <keescook@chromium.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: KFENCE: included in x86 defconfig?
Date: Wed, 7 Feb 2024 19:35:53 +0100 [thread overview]
Message-ID: <d301faa8-548e-4e8f-b8a6-c32d6a56f45b@kernel.org> (raw)
In-Reply-To: <20240207181619.GDZcPI87_Bq0Z3ozUn@fat_crate.local>
Hi Boris,
Thank you for your reply.
On 07/02/2024 19:16, Borislav Petkov wrote:
> 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?
Sorry, I'm sure I understand your suggestion: do you mean not including
KFENCE in hardening.config either, but in another one?
For the networking tests, we are already merging .config files, e.g. the
debug.config one. We are not pushing to have KFENCE in x86 defconfig, it
can be elsewhere, and we don't mind merging other .config files if they
are maintained.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-02-07 18:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 16:16 KFENCE: included in x86 defconfig? Matthieu Baerts
2024-02-07 18:05 ` Marco Elver
2024-02-07 18:16 ` Borislav Petkov
2024-02-07 18:35 ` Matthieu Baerts [this message]
2024-02-07 19:04 ` Borislav Petkov
2024-02-07 22:12 ` Matthieu Baerts
2024-02-07 22:21 ` Marco Elver
2024-02-07 23:33 ` Jakub Kicinski
2024-02-08 7:47 ` Marco Elver
2024-02-08 10:55 ` Borislav Petkov
2024-02-08 11:11 ` Linus Torvalds
2024-02-08 11:12 ` Marco Elver
2024-02-08 12:01 ` Borislav Petkov
2024-02-07 18:28 ` Matthieu Baerts
2024-02-10 6:25 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d301faa8-548e-4e8f-b8a6-c32d6a56f45b@kernel.org \
--to=matttbe@kernel.org \
--cc=bp@alien8.de \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).