lkml.org 
[lkml]   [2018]   [Jan]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [tip:x86/pti] module: Add retpoline tag to VERMAGIC
On Thu, 18 Jan 2018, Josh Poimboeuf wrote:

> On Wed, Jan 17, 2018 at 02:40:43AM -0800, tip-bot for Andi Kleen wrote:
> > Commit-ID: 6cfb521ac0d5b97470883ff9b7facae264b7ab12
> > Gitweb: https://git.kernel.org/tip/6cfb521ac0d5b97470883ff9b7facae264b7ab12
> > Author: Andi Kleen <ak@linux.intel.com>
> > AuthorDate: Tue, 16 Jan 2018 12:52:28 -0800
> > Committer: Thomas Gleixner <tglx@linutronix.de>
> > CommitDate: Wed, 17 Jan 2018 11:35:14 +0100
> >
> > module: Add retpoline tag to VERMAGIC
> >
> > Add a marker for retpoline to the module VERMAGIC. This catches the case
> > when a non RETPOLINE compiled module gets loaded into a retpoline kernel,
> > making it insecure.
> >
> > It doesn't handle the case when retpoline has been runtime disabled. Even
> > in this case the match of the retcompile status will be enforced. This
> > implies that even with retpoline run time disabled all modules loaded need
> > to be recompiled.
>
> If the user overrides the vermagic and loads the module, shouldn't we
> update the spectre_v2 sysfs vulnerability status and print a warning
> like in v2?

If the user does that then the sysfs output is not our problem anymore,
really.

Thanks,

tglx

\
 
 \ /
  Last update: 2018-01-18 18:40    [W:0.059 / U:0.156 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site