On Tue, 16 Jan 2018, Andi Kleen wrote:
> On Tue, Jan 16, 2018 at 10:24:53PM +0100, Thomas Gleixner wrote:
> > On Tue, 16 Jan 2018, Andi Kleen wrote:
> >
> > > From: Andi Kleen
> > >
> > > Add a marker for retpoline to the module VERMAGIC. This catches
> > > the case when a non RETPOLINE compile
On Tue, Jan 16, 2018 at 12:52:28PM -0800, Andi Kleen wrote:
> From: Andi Kleen
>
> 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 retpol
On Tue, Jan 16, 2018 at 10:24:53PM +0100, Thomas Gleixner wrote:
> On Tue, 16 Jan 2018, Andi Kleen wrote:
>
> > From: Andi Kleen
> >
> > 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, maki
On Tue, 16 Jan 2018, Andi Kleen wrote:
> From: Andi Kleen
>
> 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
From: Andi Kleen
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 retcompi
5 matches
Mail list logo