From: Borislav Petkov <bp@alien8.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ricardo Ribalda <ribalda@chromium.org>,
Eric Biederman <ebiederm@xmission.com>,
Baoquan He <bhe@redhat.com>, Philipp Rudo <prudo@redhat.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Ross Zwisler <zwisler@google.com>,
Simon Horman <horms@kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
linux-toolchains@vger.kernel.org
Subject: Re: [PATCH v5 2/2] x86/purgatory: Add linker script
Date: Thu, 30 Mar 2023 18:00:17 +0200 [thread overview]
Message-ID: <20230330160017.GEZCWyEXQVQZRBbYif@fat_crate.local> (raw)
In-Reply-To: <20230330113127.3011e021@gandalf.local.home>
On Thu, Mar 30, 2023 at 11:31:27AM -0400, Steven Rostedt wrote:
> On Thu, 30 Mar 2023 17:18:26 +0200
> Borislav Petkov <bp@alien8.de> wrote:
>
> > On Thu, Mar 30, 2023 at 11:15:23AM -0400, Steven Rostedt wrote:
> > > > Make sure that the .text section is not divided in multiple overlapping
> > > > sections. This is not supported by kexec_file.
> >
> > And?
> >
> > What is the failure scenario? Why are you fixing it? Why do we care?
> >
> > This is way too laconic.
> >
>
> Yeah, I think the change log in patch 1 needs to be in this patch too,
> which gives better context.
Just read it.
Why did it work with clang version < 16?
+ toolchains ML.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next parent reply other threads:[~2023-03-30 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230321-kexec_clang16-v5-0-5563bf7c4173@chromium.org>
[not found] ` <20230321-kexec_clang16-v5-2-5563bf7c4173@chromium.org>
[not found] ` <20230330111523.4b98c8ce@gandalf.local.home>
[not found] ` <20230330151826.GDZCWoQkQBj4BYbwWw@fat_crate.local>
[not found] ` <20230330113127.3011e021@gandalf.local.home>
2023-03-30 16:00 ` Borislav Petkov [this message]
2023-04-07 23:22 ` [PATCH v5 2/2] x86/purgatory: Add linker script Nick Desaulniers
2023-04-11 21:45 ` Ricardo Ribalda
2023-04-18 17:49 ` Nick Desaulniers
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=20230330160017.GEZCWyEXQVQZRBbYif@fat_crate.local \
--to=bp@alien8.de \
--cc=bhe@redhat.com \
--cc=ebiederm@xmission.com \
--cc=horms@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=prudo@redhat.com \
--cc=ribalda@chromium.org \
--cc=rostedt@goodmis.org \
--cc=x86@kernel.org \
--cc=zwisler@google.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).