From: Steven Rostedt <rostedt@goodmis.org>
To: Borislav Petkov <bp@alien8.de>
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>
Subject: Re: [PATCH v5 2/2] x86/purgatory: Add linker script
Date: Thu, 30 Mar 2023 11:31:27 -0400 [thread overview]
Message-ID: <20230330113127.3011e021@gandalf.local.home> (raw)
In-Reply-To: <20230330151826.GDZCWoQkQBj4BYbwWw@fat_crate.local>
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.
-- Steve
next prev parent reply other threads:[~2023-03-30 15:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 9:44 [PATCH v5 0/2] kexec: Fix kexec_file_load for llvm16 Ricardo Ribalda
2023-03-30 9:44 ` [PATCH v5 1/2] kexec: Support purgatories with .text.hot sections Ricardo Ribalda
2023-03-30 15:03 ` Steven Rostedt
2023-04-03 14:42 ` Philipp Rudo
2023-03-30 9:44 ` [PATCH v5 2/2] x86/purgatory: Add linker script Ricardo Ribalda
2023-03-30 15:15 ` Steven Rostedt
2023-03-30 15:18 ` Borislav Petkov
2023-03-30 15:31 ` Steven Rostedt [this message]
2023-03-30 16:00 ` Borislav Petkov
2023-04-07 23:22 ` Nick Desaulniers
2023-04-11 21:45 ` Ricardo Ribalda
2023-04-18 17:49 ` Nick Desaulniers
2023-03-31 19:13 ` Ross Zwisler
2023-04-03 15:35 ` Ricardo Ribalda
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=20230330113127.3011e021@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=ebiederm@xmission.com \
--cc=horms@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prudo@redhat.com \
--cc=ribalda@chromium.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).