stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
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 13:23:08 +0100	[thread overview]
Message-ID: <20180119122308.GA11451@kroah.com> (raw)
In-Reply-To: <p3shnd$gfb$2@blaine.gmane.org>

On Fri, Jan 19, 2018 at 10:36:29AM +0000, Francesco Del Degan wrote:
> On Fri, 19 Jan 2018 09:58:38 +0100, Greg KH wrote:
> 
> > 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?
> 
> In EOL, we will be just like others that want to provide extended 
> (custom) support, we are on our own. But that's is another problem, I 
> guess.

It's a worse problem.  Unless you duplicate the effort that the stable
maintainers do, your machines are going to be insecure.  Remember, it
takes _more_ work to maintain a kernel longer, than it did previously.
So soon you are going to be doing more work than I am, have fun!  :)

And again, why can you just not update to a newer kernel version?  Do
you have a huge out-of-tree patchset you rely on?  If so, best of luck,
you should be billing whom ever forces you to use that code as it is not
going to be easy.

good luck!

greg k-h

  reply	other threads:[~2018-01-19 12:23 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
2018-01-19 10:36       ` Francesco Del Degan
2018-01-19 12:23         ` Greg KH [this message]
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=20180119122308.GA11451@kroah.com \
    --to=greg@kroah.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).