[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190827134155.otm6ekeb53siy6lb@linux.intel.com>
Date: Tue, 27 Aug 2019 16:41:55 +0300
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Matthew Garrett <mjg59@...gle.com>, ard.biesheuvel@...aro.org
Cc: Peter Jones <pjones@...hat.com>,
Roberto Sassu <roberto.sassu@...wei.com>,
Bartosz Szczepanek <bsz@...ihalf.com>,
Lyude Paul <lyude@...hat.com>,
linux-efi <linux-efi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] efi+tpm: Don't access event->count when it isn't
mapped.
On Tue, Aug 27, 2019 at 02:03:44PM +0300, Jarkko Sakkinen wrote:
> > Jarkko, these two should probably go to 5.3 if possible - I
> > independently had a report of a system hitting this issue last week
> > (Intel apparently put a surprising amount of data in the event logs on
> > the NUCs).
>
> OK, I can try to push them. I'll do PR today.
Ard, how do you wish these to be managed?
I'm asking this because:
1. Neither patch was CC'd to linux-integrity.
2. Neither patch has your tags ATM.
/Jarkko
Powered by blists - more mailing lists