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: Sat, 9 Jul 2022 23:57:14 +0200 [thread overview]
Message-ID: <Ysn5uvBKBpcZ4j6m@zn.tnic> (raw)
In-Reply-To: <191d8f96-7573-bd0e-9ca4-3fc22c5c9a49@zytor.com>
On Sat, Jul 09, 2022 at 02:45:24PM -0700, H. Peter Anvin wrote:
> On 7/9/22 02:49, Borislav Petkov wrote:
> > On Fri, Jul 08, 2022 at 06:51:16PM -0700, H. Peter Anvin wrote:
> > > #define SETUP_ENUM_MAX SETUP_RNG_SEED
> > > #define SETUP_INDIRECT (1<<31)
> > > #define SETUP_TYPE_MAX (SETUP_ENUM_MAX | SETUP_INDIRECT)
> >
> > Wait, if we get to add a new number, SETUP_ENUM_MAX and thus
> > SETUP_TYPE_MAX will change. And they're uapi too...
>
> Talking API here rather than ABI, i.e. the semantics of those symbols.
Sure but do we worry about some userspace including those headers and
relying on the SETUP_ENUM_MAX number?
Or is userspace required to be recompiled against newer uapi headers?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-07-09 21:57 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 [this message]
2022-07-09 22:41 ` H. Peter Anvin
2022-07-10 9:45 ` Borislav Petkov
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=Ysn5uvBKBpcZ4j6m@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