[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <997ea6e0a1f2c40f429ad1f457566cdd80458c78.camel@linux.ibm.com>
Date: Wed, 11 May 2022 15:12:38 -0400
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Jonathan McDowell <noodles@...com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"x86@...nel.org" <x86@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>,
Dmitry Kasatkin <dmitry.kasatkin@...il.com>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-integrity@...r.kernel.org" <linux-integrity@...r.kernel.org>,
"linux-security-module@...r.kernel.org"
<linux-security-module@...r.kernel.org>
Subject: Re: [PATCH v3] x86/kexec: Carry forward IMA measurement log on kexec
On Wed, 2022-05-11 at 19:56 +0200, Borislav Petkov wrote:
> On Wed, May 11, 2022 at 01:53:23PM -0400, Mimi Zohar wrote:
> > This patch doesn't apply to Linus' master branch. Which tip/master
> > branch?
>
> This one:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/
thanks!
>
> Considering how the majority of the changes are x86-specific, I was
> thinking I'd carry it through the tip tree after getting your ACK for
> the IMA side of things?
Agreed, all of the changes should be architecture specific. It should
definitely be upstreamed via x86.
thanks,
Mimi
Powered by blists - more mailing lists