From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 1/3] linux: Enable Indirect Branch Tracking by default
Date: Mon, 10 Jul 2023 18:33:16 +0100 [thread overview]
Message-ID: <F748BEDF-B37B-44EF-B16F-7C3AC1739CBE@ipfire.org> (raw)
In-Reply-To: <d753cd03-007f-d78c-848e-cc72459fded8@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2175 bytes --]
Hello Peter,
I am happy with this going in, but we should also enable this in user space, too.
I will take care of this and post a patch soon. I don’t think all fits into one update, so I believe we should release this and follow up with the user space whenever suitable.
Best,
-Michael
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 9 Jul 2023, at 15:55, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> This became upstream default (see
> https://www.phoronix.com/news/Linux-IBT-By-Default-Tip for IT news media
> coverage), and given its security-relevance, we should adopt this
> setting as well.
>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> config/kernel/kernel.config.x86_64-ipfire | 2 +-
> config/rootfiles/common/x86_64/linux | 1 +
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/config/kernel/kernel.config.x86_64-ipfire b/config/kernel/kernel.config.x86_64-ipfire
> index 6c880ca8a..d70a19656 100644
> --- a/config/kernel/kernel.config.x86_64-ipfire
> +++ b/config/kernel/kernel.config.x86_64-ipfire
> @@ -431,7 +431,7 @@ CONFIG_X86_PAT=y
> CONFIG_ARCH_USES_PG_UNCACHED=y
> CONFIG_X86_UMIP=y
> CONFIG_CC_HAS_IBT=y
> -# CONFIG_X86_KERNEL_IBT is not set
> +CONFIG_X86_KERNEL_IBT=y
> CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS=y
> CONFIG_X86_INTEL_TSX_MODE_OFF=y
> # CONFIG_X86_INTEL_TSX_MODE_ON is not set
> diff --git a/config/rootfiles/common/x86_64/linux b/config/rootfiles/common/x86_64/linux
> index fb4ea3a6f..6d00654af 100644
> --- a/config/rootfiles/common/x86_64/linux
> +++ b/config/rootfiles/common/x86_64/linux
> @@ -11318,6 +11318,7 @@ etc/modprobe.d/ipv6.conf
> #lib/modules/KVER-ipfire/build/include/config/X86_INTERNODE_CACHE_SHIFT
> #lib/modules/KVER-ipfire/build/include/config/X86_IOPL_IOPERM
> #lib/modules/KVER-ipfire/build/include/config/X86_IO_APIC
> +#lib/modules/KVER-ipfire/build/include/config/X86_KERNEL_IBT
> #lib/modules/KVER-ipfire/build/include/config/X86_L1_CACHE_SHIFT
> #lib/modules/KVER-ipfire/build/include/config/X86_LOCAL_APIC
> #lib/modules/KVER-ipfire/build/include/config/X86_MCE
> --
> 2.35.3
prev parent reply other threads:[~2023-07-10 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 14:55 Peter Müller
2023-07-09 14:56 ` [PATCH 2/3] linux: Trigger a BUG() when corruption of kernel data structures is detected Peter Müller
2023-07-09 14:56 ` [PATCH 3/3] linux: Align default IOMMU handling on aarch64 Peter Müller
2023-07-10 17:33 ` Michael Tremer [this message]
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=F748BEDF-B37B-44EF-B16F-7C3AC1739CBE@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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