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: Wed, 6 Apr 2022 08:24:04 +0200 [thread overview]
Message-ID: <Yk0yBIMXQ5OCf6M1@kroah.com> (raw)
In-Reply-To: <Ykx8XWViJCKf3nGQ@zn.tnic>
On Tue, Apr 05, 2022 at 07:29:01PM +0200, Borislav Petkov wrote:
> On Mon, Apr 04, 2022 at 09:43:42AM +0200, gregkh@linuxfoundation.org wrote:
> > The patch below does not apply to the 5.16-stable tree.
>
> Really?
>
> $ git checkout -b 5.16.y stable/linux-5.16.y
> Updating files: 100% (19623/19623), done.
> branch '5.16.y' set up to track 'stable/linux-5.16.y'.
> $ git cherry-pick 4009a4ac82dd95b8cd2b62bd30019476983f0aff
> [5.16.y 045eac1dbd58] x86/sev: Unroll string mmio with CC_ATTR_GUEST_UNROLL_STRING_IO
> Author: Joerg Roedel <jroedel@suse.de>
> Date: Mon Mar 21 10:33:51 2022 +0100
> 1 file changed, 57 insertions(+), 8 deletions(-)
> $ git status
> On branch 5.16.y
> Your branch is ahead of 'stable/linux-5.16.y' by 1 commit.
> (use "git push" to publish your local commits)
>
> It works here...
And then when you build the tree:
arch/x86/lib/iomem.c: In function ‘memcpy_fromio’:
arch/x86/lib/iomem.c:90:29: error: ‘CC_ATTR_GUEST_UNROLL_STRING_IO’ undeclared (first use in this function)
90 | if (cc_platform_has(CC_ATTR_GUEST_UNROLL_STRING_IO))
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/x86/lib/iomem.c:90:29: note: each undeclared identifier is reported only once for each function it appears in
arch/x86/lib/iomem.c: In function ‘memcpy_toio’:
arch/x86/lib/iomem.c:99:29: error: ‘CC_ATTR_GUEST_UNROLL_STRING_IO’ undeclared (first use in this function)
99 | if (cc_platform_has(CC_ATTR_GUEST_UNROLL_STRING_IO))
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/x86/lib/iomem.c: In function ‘memset_io’:
arch/x86/lib/iomem.c:108:29: error: ‘CC_ATTR_GUEST_UNROLL_STRING_IO’ undeclared (first use in this function)
108 | if (cc_platform_has(CC_ATTR_GUEST_UNROLL_STRING_IO)) {
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
make[1]: *** [scripts/Makefile.build:287: arch/x86/lib/iomem.o] Error 1
I only have one "FAILED" email template, do I need another one for when
the patch applies yet breaks the build?
thanks,
greg k-h
next prev parent reply other threads:[~2022-04-06 9:52 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 [this message]
2022-04-06 11:09 ` Borislav Petkov
2022-04-18 12:01 ` Greg KH
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=Yk0yBIMXQ5OCf6M1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).