From: Matthieu Baerts <matttbe@kernel.org>
To: Alexander Potapenko <glider@google.com>,
Marco Elver <elver@google.com>,
Dmitry Vyukov <dvyukov@google.com>
Cc: kasan-dev@googlegroups.com, Netdev <netdev@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>
Subject: KFENCE: included in x86 defconfig?
Date: Wed, 7 Feb 2024 17:16:16 +0100 [thread overview]
Message-ID: <e2871686-ea25-4cdb-b29d-ddeb33338a21@kernel.org> (raw)
Hi Alexander, Marco, Dmitry,
I hope you are well!
First, thank you for your nice work with KFENCE!
When talking to Jakub about the kernel config used by the new CI for the
net tree [1], Jakub suggested [2] to check if KFENCE could not be
enabled by default for x86 architecture.
As KFENCE maintainers, what do you think about that? Do you see some
blocking points? Do you plan to add it in x86_64_defconfig?
[1] https://netdev.bots.linux.dev/status.html
[2] https://lore.kernel.org/netdev/20240207072159.33198b36@kernel.org/
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next reply other threads:[~2024-02-07 16:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 16:16 Matthieu Baerts [this message]
2024-02-07 18:05 ` KFENCE: included in x86 defconfig? Marco Elver
2024-02-07 18:16 ` Borislav Petkov
2024-02-07 18:35 ` Matthieu Baerts
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=e2871686-ea25-4cdb-b29d-ddeb33338a21@kernel.org \
--to=matttbe@kernel.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.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).