From: Dave Young <dyoung@redhat.com>
To: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, kexec@lists.infradead.org,
x86@kernel.org, linux-kernel@vger.kernel.org,
Eric Biederman <ebiederm@xmission.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Eric Richter <erichte@linux.vnet.ibm.com>
Subject: Re: [PATCH 0/6] kexec_file: Add buffer hand-over for the next kernel
Date: Wed, 22 Jun 2016 09:20:46 +0800 [thread overview]
Message-ID: <20160622012046.GD2938@dhcp-128-65.nay.redhat.com> (raw)
In-Reply-To: <1466473476-10104-1-git-send-email-bauerman@linux.vnet.ibm.com>
On 06/20/16 at 10:44pm, Thiago Jung Bauermann wrote:
> Hello,
>
> This patch series implements a mechanism which allows the kernel to pass on
> a buffer to the kernel that will be kexec'd. This buffer is passed as a
> segment which is added to the kimage when it is being prepared by
> kexec_file_load.
>
> How the second kernel is informed of this buffer is architecture-specific.
> On PowerPC, this is done via the device tree, by checking the properties
> /chosen/linux,kexec-handover-buffer-start and
> /chosen/linux,kexec-handover-buffer-end, which is analogous to how the
> kernel finds the initrd.
>
> This feature was implemented because the Integrity Measurement Architecture
> subsystem needs to preserve its measurement list accross the kexec reboot.
> This is so that IMA can implement trusted boot support on the OpenPower
> platform, because on such systems an intermediary Linux instance running as
> part of the firmware is used to boot the target operating system via kexec.
> Using this mechanism, IMA on this intermediary instance can hand over to the
> target OS the measurements of the components that were used to boot it.
We have CONFIG_KEXEC_VERIFY_SIG, why not verifying the kernel to be
loaded instead? I feel IMA should rebuild its measurement instead of
passing it to another kernel. Kexec reboot is also a reboot. If we have
to preserve something get from firmware we can do it, but other than
that I think it sounds not a good idea.
>
> Because there could be additional measurement events between the
> kexec_file_load call and the actual reboot, IMA needs a way to update the
> buffer with those additional events before rebooting. One can minimize
> the interval between the kexec_file_load and the reboot syscalls, but as
> small as it can be, there is always the possibility that the measurement
> list will be out of date at the time of reboot.
>
> To address this issue, this patch series also introduces kexec_update_segment,
> which allows a reboot notifier to change the contents of the image segment
> during the reboot process.
>
> There's one patch which makes kimage_load_normal_segment and
> kexec_update_segment share code. It's not much code that they can share
> though, so I'm not sure if it's worth including this patch.
>
> The last patch is not intended to be merged, it just demonstrates how this
> feature can be used.
>
> This series applies on top of v2 of the "kexec_file_load implementation
> for PowerPC" patch series at:
The kexec_file_load patches should be addressed first, no?
>
> http://lists.infradead.org/pipermail/kexec/2016-June/016078.html
>
> Thiago Jung Bauermann (6):
> kexec_file: Add buffer hand-over support for the next kernel
> powerpc: kexec_file: Add buffer hand-over support for the next kernel
> kexec_file: Allow skipping checksum calculation for some segments.
> kexec_file: Add mechanism to update kexec segments.
> kexec: Share logic to copy segment page contents.
> IMA: Demonstration code for kexec buffer passing.
>
> arch/powerpc/include/asm/kexec.h | 9 ++
> arch/powerpc/kernel/kexec_elf_64.c | 50 +++++++-
> arch/powerpc/kernel/machine_kexec_64.c | 64 ++++++++++
> arch/x86/kernel/crash.c | 4 +-
> arch/x86/kernel/kexec-bzimage64.c | 6 +-
> include/linux/ima.h | 11 ++
> include/linux/kexec.h | 47 +++++++-
> kernel/kexec_core.c | 205 ++++++++++++++++++++++++++-------
> kernel/kexec_file.c | 102 ++++++++++++++--
> security/integrity/ima/ima.h | 5 +
> security/integrity/ima/ima_init.c | 26 +++++
> security/integrity/ima/ima_template.c | 79 +++++++++++++
> 12 files changed, 547 insertions(+), 61 deletions(-)
>
> --
> 1.9.1
>
Thanks
Dave
next prev parent reply other threads:[~2016-06-22 1:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 1:44 [PATCH 0/6] kexec_file: Add buffer hand-over for the next kernel Thiago Jung Bauermann
2016-06-21 1:44 ` [PATCH 1/6] kexec_file: Add buffer hand-over support " Thiago Jung Bauermann
2016-06-21 1:44 ` [PATCH 2/6] powerpc: " Thiago Jung Bauermann
2016-06-21 1:44 ` [PATCH 3/6] kexec_file: Allow skipping checksum calculation for some segments Thiago Jung Bauermann
2016-06-21 1:44 ` [PATCH 4/6] kexec_file: Add mechanism to update kexec segments Thiago Jung Bauermann
2016-06-21 1:44 ` [PATCH 5/6] kexec: Share logic to copy segment page contents Thiago Jung Bauermann
2016-06-21 1:44 ` [PATCH 6/6] IMA: Demonstration code for kexec buffer passing Thiago Jung Bauermann
2016-06-22 1:20 ` Dave Young [this message]
2016-06-22 13:19 ` [PATCH 0/6] kexec_file: Add buffer hand-over for the next kernel Mimi Zohar
2016-06-22 16:34 ` 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=20160622012046.GD2938@dhcp-128-65.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=bauerman@linux.vnet.ibm.com \
--cc=ebiederm@xmission.com \
--cc=erichte@linux.vnet.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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;
as well as URLs for NNTP newsgroup(s).