From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Matthew Garrett <mjg59@google.com>, ard.biesheuvel@linaro.org
Cc: Peter Jones <pjones@redhat.com>,
Roberto Sassu <roberto.sassu@huawei.com>,
Bartosz Szczepanek <bsz@semihalf.com>,
Lyude Paul <lyude@redhat.com>,
linux-efi <linux-efi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] efi+tpm: Don't access event->count when it isn't mapped.
Date: Tue, 27 Aug 2019 16:41:55 +0300 [thread overview]
Message-ID: <20190827134155.otm6ekeb53siy6lb@linux.intel.com> (raw)
In-Reply-To: <20190827110344.4uvjppmkkaeex3mk@linux.intel.com>
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
next prev parent reply other threads:[~2019-08-27 13:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 15:30 [PATCH 1/2] efi+tpm: Don't access event->count when it isn't mapped Peter Jones
2019-08-26 15:30 ` [PATCH 2/2] efi+tpm: don't traverse an event log with no events Peter Jones
2019-08-26 16:30 ` Jarkko Sakkinen
2019-08-26 17:45 ` Matthew Garrett
2019-08-31 16:46 ` Ard Biesheuvel
2019-08-26 16:28 ` [PATCH 1/2] efi+tpm: Don't access event->count when it isn't mapped Jarkko Sakkinen
2019-08-26 17:44 ` Matthew Garrett
2019-08-27 11:03 ` Jarkko Sakkinen
2019-08-27 13:41 ` Jarkko Sakkinen [this message]
2019-08-27 16:00 ` Matthew Garrett
2019-08-27 22:11 ` Peter Jones
2019-08-29 13:21 ` Jarkko Sakkinen
2019-08-31 16:11 ` Ard Biesheuvel
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=20190827134155.otm6ekeb53siy6lb@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=ard.biesheuvel@linaro.org \
--cc=bsz@semihalf.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=mjg59@google.com \
--cc=pjones@redhat.com \
--cc=roberto.sassu@huawei.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.