public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: brijesh.singh@amd.com, thomas.lendacky@amd.com,
	stable@vger.kernel.org, "Jörg Rödel" <jroedel@suse.de>
Subject: Re: FAILED: patch "[PATCH] x86/sev: Make the #VC exception stacks part of the default" failed to apply to 5.15-stable tree
Date: Tue, 16 Nov 2021 12:52:44 +0100	[thread overview]
Message-ID: <YZObjPyuhsHmREd7@zn.tnic> (raw)
In-Reply-To: <YZOU0ViYGD24/Al0@kroah.com>

On Tue, Nov 16, 2021 at 12:24:01PM +0100, Greg KH wrote:
> Nope, planning ahead:
> 	$ ~/linux/stable/commit_tree/id_found_in 7fae4c24a2b8
> 	5.16-rc1 queue-4.4 queue-4.9 queue-4.14 queue-4.19 queue-5.4 queue-5.10 queue-5.14 queue-5.15
> 
> That commit is in the current -rc releases right now.

Bah, there's stuff in-flight.

> The problem with this commit is that the cc_platform_has() function is
> not present.  I thought about backporting it as well, but that seemed
> odd as I do not think that feature is in the 5.15 and older kernels,
> right?

The cc_platform_has() was a small set:

https://lore.kernel.org/r/YX%2B5ekjTbK3rhX%2BY@zn.tnic

which wants to keep all those checks confidential guests are going to do
around the code, sane. So you don't really need it but...

> Or is it ok to take the cc_platform_has() function?

... it will simplify all those backports which use it in the future. And
we will use cc_platform_has() from now on in common code.

In any case, we're going to backport it into SLE just for that reason -
so that it can ease backports and there's no kABI nightmares.

HTH.

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg

  reply	other threads:[~2021-11-16 11:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 10:54 FAILED: patch "[PATCH] x86/sev: Make the #VC exception stacks part of the default" failed to apply to 5.15-stable tree gregkh
2021-11-16 11:10 ` Borislav Petkov
2021-11-16 11:24   ` Greg KH
2021-11-16 11:52     ` Borislav Petkov [this message]
2021-11-16 12:50       ` Greg KH
2021-11-16 12:59         ` Borislav Petkov

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=YZObjPyuhsHmREd7@zn.tnic \
    --to=bp@suse.de \
    --cc=brijesh.singh@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox