All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Borislav Petkov <bp@suse.de>
Cc: jroedel@suse.de, stable@vger.kernel.org, thomas.lendacky@amd.com
Subject: Re: FAILED: patch "[PATCH] x86/sev: Unroll string mmio with" failed to apply to 5.16-stable tree
Date: Mon, 18 Apr 2022 14:01:03 +0200	[thread overview]
Message-ID: <Yl1S//YPDMMzyepO@kroah.com> (raw)
In-Reply-To: <Yk103F0EzAU2GkEd@zn.tnic>

On Wed, Apr 06, 2022 at 01:09:16PM +0200, Borislav Petkov wrote:
> On Wed, Apr 06, 2022 at 08:24:04AM +0200, Greg KH wrote:
> > make[1]: *** [scripts/Makefile.build:287: arch/x86/lib/iomem.o] Error 1
> 
> Bah, building is overrated.
> 
> I guess you need
> 
>   8260b9820f70 ("x86/sev: Use CC_ATTR attribute to generalize string I/O unroll")
> 
> before that.
> 
> > I only have one "FAILED" email template, do I need another one for when
> > the patch applies yet breaks the build?
> 
> I guess you could change that first sentence to
> 
> "The patch below does not apply (or build) to the X.XX-stable tree."
> 
> It seems I took it literally to mean it only doesn't apply.
> 
> :-)

Fair enough :)

So, 5.16 is now dead and end-of-life, but the original commit here still
looks to be needed in older kernels going back quite a ways.  And
8260b9820f70 ("x86/sev: Use CC_ATTR attribute to generalize string I/O
unroll") does not apply cleanly to 5.15 or older and given that it's
touching memory encryption code, I'm not comfortable guessing about the
backport.

So can you, or anyone else that cares, provide a set of backported
patches for this issue that we can apply to the stable trees?

thanks,

greg k-h

  reply	other threads:[~2022-04-18 12:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04  7:43 FAILED: patch "[PATCH] x86/sev: Unroll string mmio with" failed to apply to 5.16-stable tree gregkh
2022-04-05 17:29 ` Borislav Petkov
2022-04-06  6:24   ` Greg KH
2022-04-06 11:09     ` Borislav Petkov
2022-04-18 12:01       ` Greg KH [this message]
2022-04-27  8:27         ` Joerg Roedel

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=Yl1S//YPDMMzyepO@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bp@suse.de \
    --cc=jroedel@suse.de \
    --cc=stable@vger.kernel.org \
    --cc=thomas.lendacky@amd.com \
    /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.