Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp181395yba; Thu, 2 May 2019 23:04:52 -0700 (PDT) X-Google-Smtp-Source: APXvYqwUdGxBYivoIBqbUCwG80gWzun+JvpBL0Y+L3Qzz71R7EjalcasKqjatjCkzBCD2oSH7IYO X-Received: by 2002:a63:e451:: with SMTP id i17mr8275840pgk.312.1556863492487; Thu, 02 May 2019 23:04:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556863492; cv=none; d=google.com; s=arc-20160816; b=tceJV07i6d4Zc9y7RWHhbCptRT7/Kvqv+yjTnQz0Oi32RAa0pVPYpFDOX7cV3gM2Ac LgkOZydzHsWJsfRInMo7Az7HHTvONg7j+gcOTZ3ym6gyjSAl9M7aM7KWcm7yvR52D4bF W+gmWGX/hwgRWo4G2tfoMLSrPpYa5RpdwWI3fV9G8yrwIZ9PObrs5vcbgbdfdi21Rmra psRz+oCyQGzp+PJQewPjpNCdHgEgHsSOv/JSvJxFary2obkTMWp6Ak6JYvXUEgQ599FI 4xmjV0PWOdyXMS+Dd1/3Zsa6xfh1uMDuox+G7zHsDtOjI+dOM4gC8JcNb/qX3so/224Q 4Exw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=EWtSEcRAEClnp5qoyCUoVU+zszW981359OnvYuNYOfs=; b=OFnY5x+fYl1eC+3AliDT3Az1wpZk7vrHD0Sf2k85+nuZxqdJwcokJi04bx4zqYtapJ M/pwCC3fMYfivAxY50HpEAt0g/scbYGsYExEG/fh0psGZqslf3EbyVUkJFIOYnRDp9ri ct6vPsGsNdUSpwFzuacvotEPdWn4h29LtX7mQ0x/BZveG30BQvyi906iLSzfkevCIKkd 21imb7NW3PfdyEp9Y3ncYE7E0DrtBFIwi6CBVBWcO+munBzmo5L8wckmP2obIUSbJf4B f5N/1Qh5ZJ1WiEZwO5T2z1XIrwkHQ4HEH4+EPzkjpCaAAWsz8tcVDwakZF0xVZ2pYKQ7 DjZg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=L2+ILm3I; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n25si1135852pgv.454.2019.05.02.23.04.36; Thu, 02 May 2019 23:04:52 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=L2+ILm3I; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726599AbfECGCY (ORCPT + 99 others); Fri, 3 May 2019 02:02:24 -0400 Received: from mail-wm1-f67.google.com ([209.85.128.67]:37927 "EHLO mail-wm1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725775AbfECGCY (ORCPT ); Fri, 3 May 2019 02:02:24 -0400 Received: by mail-wm1-f67.google.com with SMTP id f2so284862wmj.3; Thu, 02 May 2019 23:02:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=EWtSEcRAEClnp5qoyCUoVU+zszW981359OnvYuNYOfs=; b=L2+ILm3IPeNDoDv54VzYglc/Z6apZqqIdA5HG/I6kne6gOBhpfCNItAibcYkaeIRlq Ap2aLXdsKMj02bBSOTh2w3DSAAru0ZGnvA88S4TBR1A+Q1KOYEm5OLZxDj7LzJxibQJu ULKNrL78nR0cEVyCAD9n08LyNyvTHx66vj3gVW+Ztx9NoWvCGgxpWJllvZobzq0PC7ql 9jnb4zg1VAWdDGlGprAizAaA0k7l8E1cvuV1UynOeOrhQB4QITyad6dKjQOQerXRT+Vd iybRWR2yzIp7fM2/4xPskqXoROzKnCanzT6pu6Lfs2C+6rp3MxGWu3vY6JLhoW7TGBlx hlpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=EWtSEcRAEClnp5qoyCUoVU+zszW981359OnvYuNYOfs=; b=t5VI1FQ5lXEZvUpMxzEM/pKyiXFXqT4IcUo+RxLMCDV6eJIG/mcNzNauHQtD4IlkpK PjB7ysFIonP9YaJEK8XmOzJBm2JY/GKcDGEJet/U09MaFHIq01E3o8petU3tIhYyqEg1 xJ+NCR0jyqJoKAG4SfpT8WYLQHMTV9Fy7L1JxEI4kBJI38l3IJHiyd6DDRJ/sQp5/hXd 7jWeX/yZ+fr2gJ0oGRo41EZq02VH07MtXBHnVbb74blpXyGpiGaBFST8aXQPzKUbLSMv MG4B95jDNUl2nVZId9NtEr7EqJiWgqyXXQutyWb1CVCE9zj+Gt4ao1IemLj7CTVffeJe cJNg== X-Gm-Message-State: APjAAAUbJLWSnIdIJST+1lgc3HK57o8BvdeNOL02PeCwVI1Pj5y+UDh2 IKYySrGVZ3PEfS57i19g8gU= X-Received: by 2002:a1c:a00f:: with SMTP id j15mr4732038wme.148.1556863341211; Thu, 02 May 2019 23:02:21 -0700 (PDT) Received: from gmail.com (2E8B0CD5.catv.pool.telekom.hu. [46.139.12.213]) by smtp.gmail.com with ESMTPSA id h81sm3494166wmf.33.2019.05.02.23.02.19 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 02 May 2019 23:02:20 -0700 (PDT) Date: Fri, 3 May 2019 08:02:18 +0200 From: Ingo Molnar To: Matthew Garrett Cc: Ard Biesheuvel , Jarkko Sakkinen , Bartosz Szczepanek , linux-integrity , Peter Huewe , Jason Gunthorpe , Roberto Sassu , linux-efi , LSM List , Linux Kernel Mailing List , =?iso-8859-1?Q?Thi=E9baud?= Weksteen Subject: Re: [PATCH V5 2/4] tpm: Reserve the TPM final events table Message-ID: <20190503060218.GA28048@gmail.com> References: <20190227202658.197113-1-matthewgarrett@google.com> <20190227202658.197113-3-matthewgarrett@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Matthew Garrett wrote: > On Thu, May 2, 2019 at 12:15 AM Ard Biesheuvel > wrote: > > > > (+ Ingo) > > > > On Tue, 30 Apr 2019 at 21:52, Matthew Garrett wrote: > > > > > > On Tue, Apr 30, 2019 at 6:07 AM Bartosz Szczepanek wrote: > > > > > > > > I may be a little late with this comment, but I've just tested these > > > > patches on aarch64 platform (from the top of jjs/master) and got > > > > kernel panic ("Unable to handle kernel read", full log at the end of > > > > mail). I think there's problem with below call to > > > > tpm2_calc_event_log_size(), where physical address of efi.tpm_log is > > > > passed as (void *) and never remapped: > > > > > > Yes, it looks like this is just broken. Can you try with the attached patch? > > > > I'm a bit uncomfortable with EFI code that is obviously broken and > > untested being queued for the next merge window in another tree. > > The patchset was Cc:ed to linux-efi@. Is there anything else I should > have done to ensure you picked it up rather than Jarkko? That's not the workflow rule the Linux kernel is using, if Cc:-ing a patchset was the only condition for upstream inclusion then we'd have a *LOT* of crap in the Linux kernel. Just applying those EFI changes without even as much as an Acked-by from the EFI maintainers is a *totally* unacceptable workflow. Please revert/rebase and re-try this on the proper submission channels. Meanwhile the broken code is NAK-ed by me: Nacked-by: Ingo Molnar Thanks, Ingo