All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Borislav Petkov <bp@suse.de>
Cc: tglx@linutronix.de, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] x86/fpu: Reset state for all signal restore failures" failed to apply to 4.4-stable tree
Date: Tue, 22 Jun 2021 12:17:15 +0200	[thread overview]
Message-ID: <YNG4q++kHwWtVupg@kroah.com> (raw)
In-Reply-To: <YNDQHgGztJAWO2H+@zn.tnic>

On Mon, Jun 21, 2021 at 07:45:02PM +0200, Borislav Petkov wrote:
> On Mon, Jun 21, 2021 at 12:52:12PM +0200, gregkh@linuxfoundation.org wrote:
> > 
> > The patch below does not apply to the 4.4-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> 
> Ok, how's this below?
> 
> It should at least capture the gist of what this commit is trying to
> achieve as the FPU mess has changed substantially since 4.4 so I'm
> really cautious here not to break any existing setups.
> 
> I've boot-tested this in a VM but Greg, I'd appreciate running it
> through some sort of stable testing framework if you're using one.

This applied to 4.4.y and 4.9.y, but we still need a 4.14.y and 4.19.y
version if at all possible.

thanks,

greg k-h

  reply	other threads:[~2021-06-22 10:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 10:52 FAILED: patch "[PATCH] x86/fpu: Reset state for all signal restore failures" failed to apply to 4.4-stable tree gregkh
2021-06-21 17:45 ` Borislav Petkov
2021-06-22 10:17   ` Greg KH [this message]
2021-06-22 20:03     ` Thomas Gleixner
2021-06-23 15:00       ` Greg KH
2021-06-23 15:04       ` Greg KH
2021-06-23 15:19         ` Thomas Gleixner

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=YNG4q++kHwWtVupg@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bp@suse.de \
    --cc=stable@vger.kernel.org \
    --cc=tglx@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.