From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Christian Gelinek <christian.gelinek@mailbox.org>
Cc: help-guix@gnu.org
Subject: Re: Intel i7-1165G7 vulnerable to Spectre v2
Date: Wed, 01 Feb 2023 16:58:30 +0100 [thread overview]
Message-ID: <87fsbpnzil.fsf@nckx> (raw)
In-Reply-To: <e7000800-bd5d-8ba4-3f45-888572fd11d8@mailbox.org>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
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?
What does Debian's kconfig list for CONFIG_BPF_UNPRIV_DEFAULT_OFF?
Guix has it *unset* (which means default *on*) which means that
unprivileged_bpf_disabled is 0 (which means *enabled*) because
Linux is a hot mess and nobody cares.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2023-02-01 16:02 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 [this message]
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=87fsbpnzil.fsf@nckx \
--to=me@tobias.gr \
--cc=christian.gelinek@mailbox.org \
--cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).