All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: speck@linutronix.de
Subject: Re: [PATCH v2 0/4] performance walnuts
Date: Thu, 7 Mar 2019 21:07:53 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.21.1903072106470.1646@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20190307141205.GA18722@kroah.com>

On Thu, 7 Mar 2019, speck for Greg KH wrote:
> On Wed, Mar 06, 2019 at 12:32:52PM -0600, speck for Mark Hatle wrote:
> > As painful as it is, we (and others) have customers on ancient kernels with no
> > way to upgrade for a variety of technical, regulatory and business reasons.  But
> > we don't expect you to start digging up old kernel and applying patches back.
> 
> And all of those kernels are almost guaranteed to be vulnerable to _WAY_
> more than just this simple issue, unless they happen to also be taking
> the stable/LTS kernel updates (or they are running a well-supported
> "enterprise" kernel).
> 
> So while it is fun for people to want to claim they "need" these
> patches, what they really "need" is to fix those
> technical/regulatory/business "reasons" to not ensure that they are
> guaranteeing they will always have broken systems.

https://bit.ly/2EWBcEZ

  parent reply	other threads:[~2019-03-07 20:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-05 21:23 [MODERATED] [PATCH v2 0/4] performance walnuts Peter Zijlstra
2019-03-05 21:23 ` [MODERATED] [PATCH v2 1/4] perf/x86/intel: Make cpuc allocations consistent Peter Zijlstra
2019-03-05 21:23 ` [MODERATED] [PATCH v2 2/4] perf/x86/intel: Generalize dynamic constraint creation Peter Zijlstra
2019-03-05 21:23 ` [MODERATED] [PATCH v2 3/4] x86: Add TSX Force Abort CPUID/MSR Peter Zijlstra
2019-03-05 21:23 ` [MODERATED] [PATCH v2 4/4] perf/x86/intel: Implement support for TSX Force Abort Peter Zijlstra
2019-03-05 22:19 ` [MODERATED] Re: [PATCH v2 0/4] performance walnuts Linus Torvalds
2019-03-05 22:26   ` Jiri Kosina
2019-03-05 22:33   ` Nelson D'Souza
2019-03-06  9:23 ` Thomas Gleixner
2019-03-06 11:56   ` [MODERATED] " Greg KH
2019-03-06 13:02     ` David Woodhouse
2019-03-06 18:08       ` Greg KH
2019-03-06 18:32         ` Mark Hatle
2019-03-07 14:12           ` Greg KH
2019-03-07 17:42             ` Mark Hatle
2019-03-07 20:07             ` Thomas Gleixner [this message]
2019-03-07 14:13     ` Greg KH
2019-03-07 21:42       ` mark gross
2019-03-07 22:06         ` Greg KH
2019-03-08  9:15           ` Jiri Kosina

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=alpine.DEB.2.21.1903072106470.1646@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=speck@linutronix.de \
    /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.