From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DBB06C3A5A4 for ; Tue, 27 Aug 2019 22:12:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id BDDCD2077B for ; Tue, 27 Aug 2019 22:12:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726111AbfH0WMG (ORCPT ); Tue, 27 Aug 2019 18:12:06 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39630 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725989AbfH0WMG (ORCPT ); Tue, 27 Aug 2019 18:12:06 -0400 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 0CAD685360; Tue, 27 Aug 2019 22:12:06 +0000 (UTC) Received: from redhat.com (dhcp-10-20-1-91.bss.redhat.com [10.20.1.91]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 86DF760CD0; Tue, 27 Aug 2019 22:12:00 +0000 (UTC) Date: Tue, 27 Aug 2019 18:11:58 -0400 From: Peter Jones To: Jarkko Sakkinen Cc: Matthew Garrett , ard.biesheuvel@linaro.org, Roberto Sassu , Bartosz Szczepanek , Lyude Paul , linux-efi , Linux Kernel Mailing List Subject: Re: [PATCH 1/2] efi+tpm: Don't access event->count when it isn't mapped. Message-ID: <20190827221157.mngkglcgj4azux7b@redhat.com> References: <20190826153028.32639-1-pjones@redhat.com> <20190826162823.4mxkwhd7mbtro3zy@linux.intel.com> <20190827110344.4uvjppmkkaeex3mk@linux.intel.com> <20190827134155.otm6ekeb53siy6lb@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190827134155.otm6ekeb53siy6lb@linux.intel.com> User-Agent: NeoMutt/20180716 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Tue, 27 Aug 2019 22:12:06 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 27, 2019 at 04:41:55PM +0300, Jarkko Sakkinen wrote: > 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. I think Ard's not back until September. I can just to re-send them with the accumulated tags and Cc linux-integrity, if you think that would help? -- Peter