From: Felix Lechner via <help-guix@gnu.org>
To: Christian Gelinek <christian.gelinek@mailbox.org>
Cc: help-guix@gnu.org
Subject: Re: Intel i7-1165G7 vulnerable to Spectre v2
Date: Wed, 1 Feb 2023 06:20:26 -0800 [thread overview]
Message-ID: <CAFHYt56pHS-jJ9vcAdg_oOTz5hn=y4ggoFZEZW4+wjiLNCdgVA@mail.gmail.com> (raw)
In-Reply-To: <e7000800-bd5d-8ba4-3f45-888572fd11d8@mailbox.org>
Hi Christian,
On Wed, Feb 1, 2023 at 2:26 AM Christian Gelinek
<christian.gelinek@mailbox.org> wrote:
>
> On the same machine, I have run Debian 11 Live from a USB drive:
>
> Vulnerability Spectre v2: Mitigation; Enhanced IBRS, IBPB
> conditional, RSB filling, PBRSB-eIBRS SW sequence
Looks like the "Enhanced IBRS" feature is not active on your machine.
Intel submitted it to the kernel in 2018. [1]
Per the comments in the code it is only needed for firmware, but still
something seems to be not quite right with our kernels—or with their
initialization after booting.
Could you please check the output of 'lscpu' after running the
following command in a Bourne-compatible shell:
echo 1 > /proc/sys/kernel/ibrs_enabled
as described here? [2]
We may have to look at the other missing features too, which are:
"IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence".
Thanks for helping to make Guix better (and safer) for everyone!
Kind regards
Felix Lechner
[1] https://lkml.iu.edu/hypermail/linux/kernel/1807.3/00923.html
[2] https://www.linuxquestions.org/questions/slackware-14/how-to-enable-ibrs-support-4175671384/
next prev parent reply other threads:[~2023-02-01 14:21 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 [this message]
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 ` Intel i7-1165G7 vulnerable to Spectre v2 Christian Gelinek
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='CAFHYt56pHS-jJ9vcAdg_oOTz5hn=y4ggoFZEZW4+wjiLNCdgVA@mail.gmail.com' \
--to=help-guix@gnu.org \
--cc=christian.gelinek@mailbox.org \
--cc=felix.lechner@lease-up.com \
/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).