From: Alexander Lobakin <alexandr.lobakin@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Alexander Lobakin <alexandr.lobakin@intel.com>,
x86@kernel.org, Dave Hansen <dave.hansen@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Jiri Slaby <jirislaby@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Tony Luck <tony.luck@intel.com>,
Kees Cook <keescook@chromium.org>,
Masahiro Yamada <masahiroy@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] x86/boot: fix relying on link order
Date: Wed, 7 Dec 2022 16:30:00 +0100 [thread overview]
Message-ID: <20221207153000.2146772-1-alexandr.lobakin@intel.com> (raw)
In-Reply-To: <Y5CwECT3a7tySawo@zn.tnic>
From: Borislav Petkov <bp@alien8.de>
Date: Wed, 7 Dec 2022 16:24:00 +0100
> On Wed, Dec 07, 2022 at 04:08:54PM +0100, Alexander Lobakin wrote:
> > I was hoping it would hit one of the 6.1 RCs as a fix,
>
> As a fix for which existing configuration which breaks if this fix is
> missing?
Ugh, fair enough :D Without it, FG-KASLR is broken, GCC-LTO is
broken, but none of them is in the mainline.
I recall there were some folks with LLD for which this $(head-y)
removal caused issues as well. But if they're quiet now, seems like
they don't hardly need it.
But not every fix is a fix only when it's easy to find a repro,
right...? But at least such are not urgent, you're correct here.
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
Thanks,
Olek
next prev parent reply other threads:[~2022-12-07 15:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 16:15 [PATCH v2 0/2] x86/boot: fix relying on link order Alexander Lobakin
2022-11-01 16:15 ` [PATCH v2 1/2] x86/boot: robustify calling startup_{32,64}() from the decompressor code Alexander Lobakin
2022-11-02 6:14 ` Jiri Slaby
2022-11-01 16:15 ` [PATCH v2 2/2] scripts/head-object-list: remove x86 from the list Alexander Lobakin
2022-11-07 12:55 ` [PATCH v2 0/2] x86/boot: fix relying on link order Alexander Lobakin
2022-11-08 23:09 ` Dave Hansen
2022-11-21 12:09 ` Alexander Lobakin
2022-11-21 13:14 ` Borislav Petkov
2022-11-21 16:00 ` Alexander Lobakin
2022-12-07 15:08 ` Alexander Lobakin
2022-12-07 15:24 ` Borislav Petkov
2022-12-07 15:30 ` Alexander Lobakin [this message]
2022-12-07 15:52 ` 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=20221207153000.2146772-1-alexandr.lobakin@intel.com \
--to=alexandr.lobakin@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jirislaby@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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 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.