From: David Woodhouse <dwmw2@infradead.org>
To: Martin Steigerwald <martin@lichtvoll.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Requirements for retpoline in Linux 4.15 (was: Re: Linux 4.15)
Date: Mon, 29 Jan 2018 11:35:25 +0000 [thread overview]
Message-ID: <1517225725.6624.136.camel@infradead.org> (raw)
In-Reply-To: <5520835.tArHHOCcxE@merkaba>
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
On Mon, 2018-01-29 at 12:19 +0100, Martin Steigerwald wrote:
>
> The whole thing works:
>
> % grep . /sys/devices/system/cpu/vulnerabilities/*
> /sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
> /sys/devices/system/cpu/vulnerabilities/spectre_v1:Vulnerable
> /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full generic
> retpoline
>
> I bet the virtualbox modules compiled by virtualbox-dkms will taint the
> support, but I bet sooner or later they will support retpoline as well.
> (Another reason to switch to KVM one day.)
As long as those are actually compiled, it should be fine. Any C code
will be built with the correct CFLAGS.
If they have explicit asm which has indirect jumps, that would still be
a problem. We just need to port objtool into the kernel and do it at
module load time, to check for that... :)
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5213 bytes --]
next prev parent reply other threads:[~2018-01-29 11:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 21:52 Linux 4.15 Linus Torvalds
2018-01-29 9:41 ` Requirements for retpoline in Linux 4.15 (was: Re: Linux 4.15) Martin Steigerwald
2018-01-29 9:53 ` David Woodhouse
2018-01-29 10:42 ` Martin Steigerwald
2018-01-29 11:19 ` Martin Steigerwald
2018-01-29 11:35 ` David Woodhouse [this message]
2018-01-30 3:43 ` Josh Poimboeuf
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=1517225725.6624.136.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@lichtvoll.de \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.