From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail.kernel.org ([198.145.29.99]) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1fKe3E-0004FJ-6O for speck@linutronix.de; Mon, 21 May 2018 08:12:08 +0200 Date: Mon, 21 May 2018 08:11:41 +0200 From: Greg KH Subject: [MODERATED] Re: Date/Time? Message-ID: <20180521061141.GB5529@kroah.com> References: <20180519172627.GB1239@kroah.com> MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: On Sun, May 20, 2018 at 11:09:08PM +0200, speck for Jiri Kosina wrote: > On Sun, 20 May 2018, speck for Jon Masters wrote: > > > * IBM p. They've an "stf-flush" patch series that protects the kernel > > stack from attack by doing (effectively) a store-to-forward buffer flush > > on entry into the kernel, patched with optimal code using alternatives. > > It's /very/ similar to the rfi-flush code, but it doesn't rely upon > > updated millicode this time. Backporting to older distros will be easier > > because the heavy lifting on the entry macros was done for older kernels > > the last time around. IBM know to contact Thomas, and should have > > already, but I will specifically remind them AGAIN to also ping Greg. I > > left the patch sending process to them. They know the parameters, etc. > > FWIW we already have the port of this to 4.12, 4.4 and 3.0 in case -stable > would like to have these before IBM submits it properly. Thanks for the offer, but I'll wait until they hit Linus's tree. Odds are Debian might want these patches, if you have them, so maybe posting them somewhere after the deadline will be helpful for them. thanks, greg k-h