From: Christian Gelinek <christian.gelinek@mailbox.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: Intel i7-1165G7 vulnerable to Spectre v2
Date: Fri, 3 Feb 2023 10:13:11 +0000 [thread overview]
Message-ID: <e89f4bb3-8035-efc9-4c98-72beec6c7bc8@mailbox.org> (raw)
In-Reply-To: <87fsbpnzil.fsf@nckx>
On 1/2/23 15:58, Tobias Geerinckx-Rice wrote:
> Christian Gelinek 写道：
>> Spectre v2: Vulnerable: eIBRS with unprivileged eBPF
> […]
>> Spectre v2: Mitigation; Enhanced IBRS, IBPB conditional, RSB filling,
>> PBRSB-eIBRS SW sequence
>
> Does
>
> $ echo 1 | sudo tee /proc/sys/kernel/unprivileged_bpf_disabled
>
> change this?
It does, thank you! This is the updated output line of `lscpu`:
Spectre v2: Mitigation; Enhanced IBRS, IBPB conditional, RSB filling,
PBRSB-eIBRS SW sequence
which matches the output I saw when I was running Debian 11.
How can I make this change permanent, ideally surviving both reboots as
well as `guix system reconfigure` invocations?
Or do we think this will be soon compiled into the kernel, if I
understood Remco's message [0] and your response [1] to that correctly,
and therefore coming "for free" (for me, anyway) by `reconfigure`ing?
Kinde regards,
Christian
[0]: https://lists.gnu.org/archive/html/help-guix/2023-02/msg00008.html
[1]: https://lists.gnu.org/archive/html/help-guix/2023-02/msg00009.html
prev parent reply other threads:[~2023-02-03 10:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 10:21 Intel i7-1165G7 vulnerable to Spectre v2 Christian Gelinek
2023-02-01 14:20 ` Felix Lechner via
2023-02-03 9:59 ` Christian Gelinek
2023-02-01 15:58 ` Tobias Geerinckx-Rice
2023-02-01 18:29 ` Ekaitz Zarraga
2023-02-01 19:43 ` Disabling unprivileged BPF by default in our kernels Tobias Geerinckx-Rice
2023-02-02 11:40 ` Leo Famulari
2023-02-02 17:13 ` Remco van 't Veer
2023-02-02 17:19 ` Tobias Geerinckx-Rice
2023-02-03 10:13 ` Christian Gelinek [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e89f4bb3-8035-efc9-4c98-72beec6c7bc8@mailbox.org \
--to=christian.gelinek@mailbox.org \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).