public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Corey Minyard <cminyard@mvista.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Backport of KPTI to 2.6.32 available
Date: Thu, 11 Jan 2018 21:32:13 +0100	[thread overview]
Message-ID: <20180111203213.GA301@kroah.com> (raw)
In-Reply-To: <62683052-9333-b2af-4230-241388c3bc31@mvista.com>

On Thu, Jan 11, 2018 at 11:42:38AM -0600, Corey Minyard wrote:
> I've completed a backport of KPTI from linux-stable-3.2.y to 2.6.32.71, in
> case anyone is interested and wants to avoid all the work I went through.
> It's available at:
> 
> https://github.com/MontaVista-OpenSourceTechnology/linux-nonlts-secfix.git
> linux-2.6.32-secfix
> 
> I'll try to keep it up to date with fixes andn with Spectre fixes.

That's crazy, why update it now, when it's missing hundreds, if not
thousands, of other much more severe security fixes?  What makes this
one more "urgent" than all of the others?

Anyway, anyone running this branch is getting a very false sense of "I'm
running a fixed kernel!"  I strongly recommend it not be used for
anything...

> A 3.10 branch will hopefully be coming, too.

Again, why?  There's backports for this in the android-common tree if
you really want it.  But again, you really do not.

thanks,

greg k-h

  parent reply	other threads:[~2018-01-11 20:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11 17:42 Backport of KPTI to 2.6.32 available Corey Minyard
2018-01-11 17:55 ` Willy Tarreau
2018-01-11 20:32 ` Greg KH [this message]
2018-01-11 21:10   ` Corey Minyard

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=20180111203213.GA301@kroah.com \
    --to=greg@kroah.com \
    --cc=cminyard@mvista.com \
    --cc=linux-kernel@vger.kernel.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