From: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Stewart Smith <stewart@linux.vnet.ibm.com>,
"H. Peter Anvin" <hpa@zytor.com>, Baoquan He <bhe@redhat.com>,
Dave Young <dyoung@redhat.com>,
x86@kernel.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Eric Biederman <ebiederm@xmission.com>,
Michael Ellerman <mpe@ellerman.id.au>,
linux-ima-devel@lists.sourceforge.net,
Andrew Morton <akpm@linux-foundation.org>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
Thomas Gleixner <tglx@linutronix.de>,
Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH v5 1/5] kexec_file: Include the purgatory segment in the kexec image checksum.
Date: Wed, 14 Sep 2016 22:51:36 -0300 [thread overview]
Message-ID: <4542776.bqQjVnlNjh@hactar> (raw)
In-Reply-To: <20160915114308.19195f71@canb.auug.org.au>
Hello Stephen,
Am Donnerstag, 15 September 2016, 11:43:08 schrieb Stephen Rothwell:
> Hi Thiago,
>
> > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> > index 2a1f0ce7c59a..dcd1679f3005 100644
> > --- a/arch/x86/Kconfig
> > +++ b/arch/x86/Kconfig
> > @@ -1792,6 +1792,11 @@ config SECCOMP
> >
> > source kernel/Kconfig.hz
> >
> > +# x86 needs to relocate the purgatory after the checksum is calculated,
> > +# therefore the purgatory cannot be part of the kexec image checksum.
> > +config ARCH_MODIFIES_KEXEC_PURGATORY
> > + bool
> > +
>
> The above should probably be in arch/Kconfig (with an appropriately
> changed comment) since it is used in generic code.
Thanks for your quick response! I'll make that change tomorrow and send an
updated version of just this patch.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2016-09-15 1:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 0:54 [PATCH v5 0/5] kexec_file: Add buffer hand-over for the next kernel Thiago Jung Bauermann
2016-09-15 0:54 ` [PATCH v5 1/5] kexec_file: Include the purgatory segment in the kexec image checksum Thiago Jung Bauermann
2016-09-15 1:43 ` Stephen Rothwell
2016-09-15 1:51 ` Thiago Jung Bauermann [this message]
2016-09-15 15:55 ` Thiago Jung Bauermann
2016-09-15 0:54 ` [PATCH v5 2/5] kexec_file: Add buffer hand-over support for the next kernel Thiago Jung Bauermann
2016-09-15 0:54 ` [PATCH v5 3/5] powerpc: " Thiago Jung Bauermann
2016-09-15 0:54 ` [PATCH v5 4/5] kexec_file: Add mechanism to update kexec segments Thiago Jung Bauermann
2016-09-15 0:54 ` [PATCH v5 5/5] IMA: Demonstration code for kexec buffer passing Thiago Jung Bauermann
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=4542776.bqQjVnlNjh@hactar \
--to=bauerman@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=linux-ima-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=sfr@canb.auug.org.au \
--cc=stewart@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
--cc=x86@kernel.org \
--cc=zohar@linux.vnet.ibm.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