From: Andrew Morton <akpm@linux-foundation.org>
To: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Eric Biederman <ebiederm@xmission.com>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: ima measurement carrying on -mm
Date: Thu, 29 Sep 2016 14:02:06 -0700 [thread overview]
Message-ID: <20160929140206.bc37b32cd63d9635682274c8@linux-foundation.org> (raw)
In-Reply-To: <1687520.U903BamSQx@hactar>
On Thu, 29 Sep 2016 17:44:10 -0300 Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com> wrote:
> Hello Andrew,
>
> You have in the -mm tree a version of the "kexec handover buffer" and "ima
> carry measurement list" patches that were NAKed by Eric Biederman. I would
> just like to double-check that there's no risk of that version reaching
> v4.9.
>
> Mimi posted v5 of a merged patch set that addresses Eric's concern:
>
> https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-September/149183.html
>
> There are no separate kexec handover patches anymore. They were folded into
> the series above. The kexec code is simplified now, it doesn't support
> updating the buffer and recalculating the hash on reboot, and is now IMA-
> specific instead of a generic kexec feature.
Yup, thanks.
I wasn't thinking any of this material is suitable for 4.9. Seems that
a bit more consideration will be needed. Am I wrong about that?
Are all of these -mm patches up to date?
kexec_file-allow-arch-specific-memory-walking-for-kexec_add_buffer.patch
kexec_file-change-kexec_add_buffer-to-take-kexec_buf-as-argument.patch
kexec_file-factor-out-kexec_locate_mem_hole-from-kexec_add_buffer.patch
powerpc-change-places-using-config_kexec-to-use-config_kexec_core-instead.patch
powerpc-factor-out-relocation-code-from-module_64c-to-elf_util_64c.patch
powerpc-generalize-elf64_apply_relocate_add.patch
powerpc-adapt-elf64_apply_relocate_add-for-kexec_file_load.patch
powerpc-add-functions-to-read-elf-files-of-any-endianness.patch
powerpc-implement-kexec_file_load.patch
powerpc-add-code-to-work-with-device-trees-in-kexec_file_load.patch
powerpc-add-support-for-loading-elf-kernels-with-kexec_file_load.patch
powerpc-add-support-for-loading-elf-kernels-with-kexec_file_load-fix.patch
powerpc-add-purgatory-for-kexec_file_load-implementation.patch
powerpc-add-purgatory-for-kexec_file_load-implementation-fix.patch
powerpc-enable-config_kexec_file-in-powerpc-server-defconfigs.patch
#
kexec_file-include-the-purgatory-segment-in-the-kexec-image-checksum.patch
kexec_file-add-buffer-hand-over-support-for-the-next-kernel.patch
powerpc-kexec_file-add-buffer-hand-over-support-for-the-next-kernel.patch
kexec_file-add-mechanism-to-update-kexec-segments.patch
next prev parent reply other threads:[~2016-09-29 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 20:44 ima measurement carrying on -mm Thiago Jung Bauermann
2016-09-29 21:02 ` Andrew Morton [this message]
2016-09-29 21:29 ` Thiago Jung Bauermann
2016-09-29 21:53 ` Eric W. Biederman
2016-09-29 22:16 ` Thiago Jung Bauermann
2016-09-29 21:47 ` Eric W. Biederman
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=20160929140206.bc37b32cd63d9635682274c8@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bauerman@linux.vnet.ibm.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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 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.