Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp933607ybn; Wed, 25 Sep 2019 09:47:26 -0700 (PDT) X-Google-Smtp-Source: APXvYqwYezbYJlIKAk04kPttXxbCM17AojLQeznMBkYco/gUDO6E1G8T/AUlknA9G8MsI5tcM6Pt X-Received: by 2002:a17:906:6d4:: with SMTP id v20mr132293ejb.223.1569430045887; Wed, 25 Sep 2019 09:47:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569430045; cv=none; d=google.com; s=arc-20160816; b=VtcX8w6ZgL/WNdTtUP2IvP2o6VgetIKHUr+84WdvRZLe6sUTIhRnaZRbWXz5aO0ekS GNHRdlVhEQqhCZhXWjg3ckmhYW6uNZlzhVEAy2hww4CtBZWu++SzFjaQKfy4IefA+dWB cc94VoNTb1BFv2n6XqJQCD6v2JIK/PZtIOHu/m3anLiXEh+1zDZAbRhUHkvzBWMOivJc crQ+fvCb+aCR33R5SCXo3LS++mD+0v3AV8NQP/EWG7ZO+A5JbewTp0gTqNQqB5Z+0IHA WMy9pDlocS7qBRF/MU5W3xuJhibKzuDoJeVUWHjfeT0icvl8A8xpPyzoYeGGJtReUuKk r4kg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-disposition :content-transfer-encoding:user-agent:in-reply-to:mime-version :references:mail-followup-to:reply-to:message-id:subject:cc:to:from :date:dkim-signature; bh=brtnUNEATJxaiEmZJMG7ZyzZu+Ldb+R0Iih2eWtZNa8=; b=0jg8MhPmucpdNM7LU70IzoS3iZ3mxDYshLYN4U6tRqeF8zs7gWR7zbvoDacUqQSRFw KCSrPgwnE/Oi9R+w7cINN2Ed6W2IJ3q1sMtmLIRZmffU1XUUePO9+LjlhhWNbE2dV77y DxSfb2XqN9SU4YuD7MRydPUTeuFwVF2WXw2AF+a3weBBJ3RSSJQrgmC23XcpZNHb/qqW 3q5rHpOMUUd89UG1FGVDYA2STakq1Bo75MyrjRsv9Z3jhfx3Qqf7J7GCcAP+rvRavd2z w5945Tatuu1itzXRToQj/WZjffJwNOjJ+4omhfpVW1Z9bC6DdrukBl4Ajtnw/LV6+faL YSDQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=CvIurzkU; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c12si3772006edb.394.2019.09.25.09.47.01; Wed, 25 Sep 2019 09:47:25 -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=pass header.i=@redhat.com header.s=mimecast20190719 header.b=CvIurzkU; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2405424AbfIWRKQ (ORCPT + 99 others); Mon, 23 Sep 2019 13:10:16 -0400 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:36398 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1732910AbfIWRKP (ORCPT ); Mon, 23 Sep 2019 13:10:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1569258614; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=brtnUNEATJxaiEmZJMG7ZyzZu+Ldb+R0Iih2eWtZNa8=; b=CvIurzkUgXXwWaeRZFHy9j301sh+XRjQ129axRbcz3vxYFAltnTcG+DS10099kKtvNAnWm hyAZ0mDMFjBhAqdZoio/LZFJNydHiaBpDSKBNHQiHt3PEbZOizDET2hG4HOPPjkOXrVTiB ZeymYIv3TDz4WM1/u9bTNwcvWatQKUI= Received: from mail-io1-f70.google.com (mail-io1-f70.google.com [209.85.166.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-247-fNfUA78ZPEO3DDUuqgQ4vQ-1; Mon, 23 Sep 2019 13:10:13 -0400 Received: by mail-io1-f70.google.com with SMTP id m3so24518191ion.11 for ; Mon, 23 Sep 2019 10:10:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:reply-to :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=rh1uvaNsooagBW4WOK11wp/OzNbWIxJmJoNftck7Ang=; b=ef/BQiNpkD1F1ezldh4OJRPna0IOXBXwo9j7SBhxZ0pOgDL+Uj5vWC1TCWxEkUMfJa zrRtgG/97yZH6Lyu21Yx7XzhJVq23CuqeZ/5+U/qdZYKJkLSTHaPV47nNiCercSqUmg8 iYOwuMcO4Uf784xnM2Iog0kSELsLnHgtU5ZRczXgo0B9uowDAzShZ9rLZHu4eEi6Nm3z y/i8BSNvLhv9f8xPARwSjI5BrbKb7VoeU4f7tHnQvmrojdQWzWf86b/4UIyaCDoLbfQs Zhlz8TFm5FKVA5ECRexQPE8TptUxNfV0fPM1hvstWRI56palTFIF2XZUZEG9CQxFNt9y QOig== X-Gm-Message-State: APjAAAVL98WxQfHJr0cTvbsm+lBP+4LUsigO+U/hTZjcfGEsBY5uRhmu TGDx9s9KHm0UR4kIED+Mk3DJRLpqlAXPLNGN+ug2DOFooDGXg2mTC4w5tHraLTz5wJLFAJHCRKj 0h9w5yu7JkuUgV5Z9j80BJI5z X-Received: by 2002:a5e:9917:: with SMTP id t23mr308427ioj.141.1569258612799; Mon, 23 Sep 2019 10:10:12 -0700 (PDT) X-Received: by 2002:a5e:9917:: with SMTP id t23mr308405ioj.141.1569258612538; Mon, 23 Sep 2019 10:10:12 -0700 (PDT) Received: from localhost (ip70-163-223-149.ph.ph.cox.net. [70.163.223.149]) by smtp.gmail.com with ESMTPSA id w7sm11707131iob.17.2019.09.23.10.10.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 23 Sep 2019 10:10:11 -0700 (PDT) Date: Mon, 23 Sep 2019 10:10:10 -0700 From: Jerry Snitselaar To: linux-efi@vger.kernel.org Cc: linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org, Matthew Garrett , Ard Biesheuvel , Jarkko Sakkinen Subject: Re: [RFC PATCH] tpm: only set efi_tpm_final_log_size after successful event log parsing Message-ID: <20190923171010.csz4js3xs2mixmpq@cantor> Reply-To: Jerry Snitselaar Mail-Followup-To: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org, Matthew Garrett , Ard Biesheuvel , Jarkko Sakkinen References: <20190918191626.5741-1-jsnitsel@redhat.com> MIME-Version: 1.0 In-Reply-To: <20190918191626.5741-1-jsnitsel@redhat.com> User-Agent: NeoMutt/20180716 X-MC-Unique: fNfUA78ZPEO3DDUuqgQ4vQ-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=WINDOWS-1252; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Any thoughts on this? I know of at least 2 Lenovo models that are running into this problem. In the case of the one I have currently have access to the problem is that the hash algorithm id for an event isn't one that is currently in the TCG registry, and it fails to find a match when walking the digest_sizes array. That seems like an issue for the vendor to fix in the b= ios, but we should look at the return value of tpm2_calc_event_log_size and not stick a negative value in efi_tpm_final_log_size.