public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
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 18:55:14 +0100	[thread overview]
Message-ID: <20180111175514.GD15344@1wt.eu> (raw)
In-Reply-To: <62683052-9333-b2af-4230-241388c3bc31@mvista.com>

Hi Corey,

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

Well, good job on this, thanks for sharing! However, this is just a friendly
reminder to everyone still running 2.6.32 that during my 3.10 maintenance
period after I dropped 2.6.32, I saw a significant number of bugs affecting
older versions, 2.6.32 included. So if people are using your branch above to
pick your patches and apply them to their locally maintained kernel, that's
possibly fine. However please guys don't run just the kernel above as-is as
it's definitely missing a few hundreds of fixes (~1300 were fixed in 3.10
since 2.6.32.71 was released, some addressing local privilege escalations).

Cheers,
Willy

  reply	other threads:[~2018-01-11 17:55 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 [this message]
2018-01-11 20:32 ` Greg KH
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=20180111175514.GD15344@1wt.eu \
    --to=w@1wt.eu \
    --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