From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com ([66.111.4.25]:38223 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755256AbeASMXQ (ORCPT ); Fri, 19 Jan 2018 07:23:16 -0500 Date: Fri, 19 Jan 2018 13:23:08 +0100 From: Greg KH To: Francesco Del Degan Cc: stable@vger.kernel.org Subject: Re: KPTI for 4.1 LTS Message-ID: <20180119122308.GA11451@kroah.com> References: <20180118094017.GA28652@kroah.com> <20180119085838.GA31700@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: stable-owner@vger.kernel.org List-ID: 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