From: Greg KH <gregkh@linuxfoundation.org>
To: Francesco Del Degan <f.deldegan@pr0gg3d.net>
Cc: stable@vger.kernel.org
Subject: Re: KPTI for 4.1 LTS
Date: Fri, 19 Jan 2018 09:58:38 +0100 [thread overview]
Message-ID: <20180119085838.GA31700@kroah.com> (raw)
In-Reply-To: <p3s98e$gfb$1@blaine.gmane.org>
On Fri, Jan 19, 2018 at 08:11:58AM +0000, Francesco Del Degan wrote:
> On Thu, 18 Jan 2018 10:40:17 +0100, Greg KH wrote:
>
> > Ick, why would you be using a kernel that is about to be end-of-life
> > anyway? Why can't you use 4.9 or even better, 4.14?
>
> Since we mantain a custom distro, upgrading to a different major kernel
> version is not an option atm (QA, etc).
Really? What are you going to do when this goes end-of-life in 3
months? Seems like you should already be planning for that, right?
Also, you should always be able to run a new kernel on an old distro
with no problems, we made that guarantee over a decade ago and have not
broken it that I know of. If something breaks, let us know.
> I was asking just because we saw that some distro based on 4.1 as well
> (Oracle linux, etc) have patched it on its own, so we wondered if
> something more upstream would have been available before starting our
> backporting efforts too.
>
> Due to particular nature of vulnerability I was expected that at least
> this would be patched in all *current* LTS (the 3.2 that shares the same
> EOL date was patched like 10 days ago).
If you will note, different people maintain the different trees, and
they all have different amounts of time they can devote to this:
https://www.kernel.org/category/releases.html
If you were to provide working patches for 4.1, I'm sure that would make
things go quicker :)
thanks,
greg k-h
next prev parent reply other threads:[~2018-01-19 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 8:16 KPTI for 4.1 LTS Francesco Del Degan
2018-01-18 9:40 ` Greg KH
2018-01-19 8:11 ` Francesco Del Degan
2018-01-19 8:58 ` Greg KH [this message]
2018-01-19 10:36 ` Francesco Del Degan
2018-01-19 12:23 ` Greg KH
2018-01-19 17:00 ` Willy Tarreau
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=20180119085838.GA31700@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=f.deldegan@pr0gg3d.net \
--cc=stable@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 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.