From: Borislav Petkov <bp@alien8.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, X86 ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>
Subject: Re: [PATCH tip v8] x86/setup: Use rng seeds from setup_data
Date: Sun, 10 Jul 2022 11:45:28 +0200 [thread overview]
Message-ID: <YsqfuPeB5jhFU9g5@zn.tnic> (raw)
In-Reply-To: <8e5eb2db-ce31-3dc8-8f75-3959036686f8@zytor.com>
On Sat, Jul 09, 2022 at 03:41:19PM -0700, H. Peter Anvin wrote:
> In ABI/API terms, that symbol has the semantic of connecting the API version
> to the underlying ABI version; a piece of code that sees an enumeration type
> > SETUP_ENUM_MAX must by definition treat it as an opaque blob. In the
> future, should it become warranted, we may add flags that indicate how
> unaware code should handle them, but I don't think we can engineer that
> right now.
Ok, let's hope it doesn't come to that and userspace behaves... <eyeroll>
So, I'm going to send the below to Linus now so that 5.19 releases fixed
and then queue Jason's patch next week.
Thx.
---
From: Borislav Petkov <bp@suse.de>
Date: Sun, 10 Jul 2022 11:15:47 +0200
Subject: [PATCH] x86/boot: Fix the setup data types max limit
Commit in Fixes forgot to change the SETUP_TYPE_MAX definition which
contains the highest valid setup data type.
Correct that.
Fixes: 5ea98e01ab52 ("x86/boot: Add Confidential Computing type to setup_data")
Signed-off-by: Borislav Petkov <bp@suse.de>
Link: https://lore.kernel.org/r/ddba81dd-cc92-699c-5274-785396a17fb5@zytor.com
---
arch/x86/include/uapi/asm/bootparam.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/include/uapi/asm/bootparam.h b/arch/x86/include/uapi/asm/bootparam.h
index bea5cdcdf532..e02a8a8ef23c 100644
--- a/arch/x86/include/uapi/asm/bootparam.h
+++ b/arch/x86/include/uapi/asm/bootparam.h
@@ -15,7 +15,7 @@
#define SETUP_INDIRECT (1<<31)
/* SETUP_INDIRECT | max(SETUP_*) */
-#define SETUP_TYPE_MAX (SETUP_INDIRECT | SETUP_JAILHOUSE)
+#define SETUP_TYPE_MAX (SETUP_INDIRECT | SETUP_CC_BLOB)
/* ram_size flags */
#define RAMDISK_IMAGE_START_MASK 0x07FF
--
2.35.1
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-07-10 9:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 11:33 [PATCH] x86/setup: Allow passing RNG seeds via e820 setup table Jason A. Donenfeld
2022-06-30 11:59 ` [PATCH v2] " Jason A. Donenfeld
2022-06-30 12:09 ` [PATCH v3] " Jason A. Donenfeld
2022-06-30 13:31 ` [PATCH v4] " Jason A. Donenfeld
2022-07-01 17:58 ` [PATCH v5] " Jason A. Donenfeld
2022-07-01 18:25 ` H. Peter Anvin
2022-07-01 18:42 ` Jason A. Donenfeld
2022-07-01 18:52 ` H. Peter Anvin
2022-07-01 18:53 ` Jason A. Donenfeld
2022-07-03 0:44 ` [PATCH v6] x86/setup: Use rng seeds from setup_data Jason A. Donenfeld
2022-07-07 0:08 ` [PATCH v7] " Jason A. Donenfeld
2022-07-08 11:39 ` [PATCH tip v8] " Jason A. Donenfeld
2022-07-09 1:51 ` H. Peter Anvin
2022-07-09 9:43 ` Jason A. Donenfeld
2022-07-09 9:48 ` [PATCH tip v9] " Jason A. Donenfeld
2022-07-09 22:42 ` H. Peter Anvin
2022-07-09 23:23 ` Jason A. Donenfeld
2022-07-09 9:49 ` [PATCH tip v8] " Borislav Petkov
2022-07-09 9:53 ` Jason A. Donenfeld
2022-07-09 10:21 ` Borislav Petkov
2022-07-09 21:45 ` H. Peter Anvin
2022-07-09 21:57 ` Borislav Petkov
2022-07-09 22:41 ` H. Peter Anvin
2022-07-10 9:45 ` Borislav Petkov [this message]
2022-07-10 11:11 ` Jason A. Donenfeld
2022-07-10 12:27 ` Borislav Petkov
2022-07-10 17:13 ` Jason A. Donenfeld
2022-07-10 17:29 ` [PATCH tip v10] " Jason A. Donenfeld
2022-07-11 9:39 ` [tip: x86/kdump] " tip-bot2 for Jason A. Donenfeld
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=YsqfuPeB5jhFU9g5@zn.tnic \
--to=bp@alien8.de \
--cc=Jason@zx2c4.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®