Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp6212320ybc; Wed, 27 Nov 2019 17:24:02 -0800 (PST) X-Google-Smtp-Source: APXvYqyX5YJvsUcafuMOuwrzmV906KHNbWbCBP+XA5UALUlfXjlrwgXulE0P/ICsA6ypapSYrf+K X-Received: by 2002:aa7:c453:: with SMTP id n19mr18343494edr.103.1574904242496; Wed, 27 Nov 2019 17:24:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574904242; cv=none; d=google.com; s=arc-20160816; b=LRcNse4M+ChdPCkGqkxI3/9bJk7AoY4al7W34op1sWyh/gcKgIbq4ZpFydxehdVBrr Ngv/Whlmi2uqltk0pGJcIQphtwTQxiP2v6JFB0wFX7jCkMULfAq2SZ3EmcWMPY/EDbNW OsweGzFor6jHj47KCBAd2QTn285PzE5Ug5AVrjOEH/vCX7YBzBwMAuw5hGnhWnKzyNz2 d4zazYr9Wxi2cMQetdvkvuwakabk7qQCYcxA1anZNTBQF8q0Sbs6Mt/lwWNQrfCJZvHO 1MLuLX3FSs9HlvDntVnCPByJb2WN5QxdvlpHmS82dFcbdJJGaBuK3kNrtOKveR2E9e7B VSng== 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:in-reply-to:mime-version:references :mail-followup-to:reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=/HFDV1dFXXc1XWLJ2qEUSb2HH9ThLGZlFl18InpcbEM=; b=v/7r9jmO9prwTlxYJT0noXXtj+1Nh2iqTd8uczWO6lXyaZmQ+MBZbIwhEfMk0Rp4bu ZoIlesHpIaHyCg1pzLrXTF4GblQjkdDHIJ2iXW1QR3qtyZGS5dOlGb7mQGLBCah78LCd E87b16Zhpak03U7CnckkZEY3RHg6OGQTL+Vydm1nXZ6jdVEpucQa9/oXSSyfPq4rKGzV rVPvMn8Z6nS18FSW1cQFGZbvU+RL82AM7TIxYZAlEVfsSGrGdITz8LCjLEy8xhSrgc0f 42DmhCllcMlCVHKCM8qYi6p2sDzxa42XUuEole2Cqm5VFR3Waevfyo8a8wTPzMt4vRJf /I0w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=CfSkWerG; 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 ce11si13058392edb.391.2019.11.27.17.23.37; Wed, 27 Nov 2019 17:24:02 -0800 (PST) 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=CfSkWerG; 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 S1727545AbfK1BVP (ORCPT + 99 others); Wed, 27 Nov 2019 20:21:15 -0500 Received: from us-smtp-2.mimecast.com ([207.211.31.81]:23152 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726984AbfK1BVP (ORCPT ); Wed, 27 Nov 2019 20:21:15 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1574904073; 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=/HFDV1dFXXc1XWLJ2qEUSb2HH9ThLGZlFl18InpcbEM=; b=CfSkWerGyNhkq4puZkAZhxsmhlHWdA+yZB3LN20I8wEoCzsfaWHkbHW2b6Y5VICM5IXBEz tRofnzeZ+9Ii7ZrbkloCS3+wW2VAdZWW9o7qGMULL+hDGpC5Z3pmRRG8Svx+qvTnF83VJB oK1sLwX89n7/Oq+itSO/MU4rKVah68A= Received: from mail-pg1-f199.google.com (mail-pg1-f199.google.com [209.85.215.199]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-307-PHT3JJawMZiid-DUrE4Raw-1; Wed, 27 Nov 2019 20:21:10 -0500 Received: by mail-pg1-f199.google.com with SMTP id r2so3274138pgl.4 for ; Wed, 27 Nov 2019 17:21:10 -0800 (PST) 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; bh=vTEn0L1tG99iZM5cLflAm0RZ2oMnvmDu1+wuwMQxkUM=; b=tisJCSyngdlozpa8jFi3snSUU8uaD3sZKXx8H0YY3yOSEwdEnfmcG/HosQ/8U+FRd+ Wm0Kms6t6O2DrgOrgOUHOiIxJoFB2Je/nf9h6ZM3BU8bBygAwJfN2M8CpXENdDZ5u2mt lpkY0IgKcIXORPjkDQsqB6UJnZR6AHIwOttC90u0D3H/I0gEUl0AoTpyHbE18+1/Ug38 YXqgxs4822tmF/Jq/CwyCVXWsQwVsCxmFZmqUzbRIc/V80zmJXtvN4CqB8qyshz+qn5N TMoOEKAQNkTRe95ajlpQlEqBWMB3q1RTsXSjmxnHtEs5R2cBVPF9/IijPRA1/dejBRo8 AaKw== X-Gm-Message-State: APjAAAXzxkyeMnJzpx483JtJUsGvsoC9OoPt6kERWB3E06s+MgC1oN7j Rsb9EQ35lYWRFOyNOvJOAiZLenPN8NTKO8bGDicABPiZP9hhhew4j6W/gyplpWrLR+iej4Kk0rI lLpt8RQtVu7jPM++/2NwheCEo X-Received: by 2002:a17:90a:2ec1:: with SMTP id h1mr6483432pjs.135.1574904068882; Wed, 27 Nov 2019 17:21:08 -0800 (PST) X-Received: by 2002:a17:90a:2ec1:: with SMTP id h1mr6483414pjs.135.1574904068578; Wed, 27 Nov 2019 17:21:08 -0800 (PST) Received: from localhost (ip70-163-223-149.ph.ph.cox.net. [70.163.223.149]) by smtp.gmail.com with ESMTPSA id u26sm2722140pfn.46.2019.11.27.17.21.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Nov 2019 17:21:07 -0800 (PST) Date: Wed, 27 Nov 2019 18:20:55 -0700 From: Jerry Snitselaar To: Jarkko Sakkinen Cc: Dan Williams , Linus Torvalds , Linux Kernel Mailing List , linux-integrity@vger.kernel.org, James Morris , Stefan Berger , stable Subject: Re: [GIT PULL] tpmdd updates for Linux v5.4 Message-ID: <20191128012055.f3a6gq7bjpvuierx@cantor> Reply-To: Jerry Snitselaar Mail-Followup-To: Jarkko Sakkinen , Dan Williams , Linus Torvalds , Linux Kernel Mailing List , linux-integrity@vger.kernel.org, James Morris , Stefan Berger , stable References: <20190902143121.pjnykevzlajlcrh6@linux.intel.com> <20191127205800.GA14290@linux.intel.com> <20191127205912.GB14290@linux.intel.com> MIME-Version: 1.0 In-Reply-To: <20191127205912.GB14290@linux.intel.com> X-MC-Unique: PHT3JJawMZiid-DUrE4Raw-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=utf-8; 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 On Wed Nov 27 19, Jarkko Sakkinen wrote: >On Wed, Nov 27, 2019 at 10:58:00PM +0200, Jarkko Sakkinen wrote: >> On Wed, Nov 20, 2019 at 08:48:25PM -0800, Dan Williams wrote: >> > On Mon, Sep 2, 2019 at 7:34 AM Jarkko Sakkinen >> > wrote: >> > > >> > > Hi >> > > >> > > A new driver for fTPM living inside ARM TEE was added this round. In >> > > addition to that, there is three bug fixes and one clean up. >> > > >> > > /Jarkko >> > > >> > > The following changes since commit 8fb8e9e46261e0117cb3cffb6dd8bb7e0= 8f8649b: >> > > >> > > Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel= /git/rdma/rdma (2019-08-30 09:23:45 -0700) >> > > >> > > are available in the Git repository at: >> > > >> > > git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-next-= 20190902 >> > > >> > > for you to fetch changes up to e8bd417aab0c72bfb54465596b16085702ba0= 405: >> > > >> > > tpm/tpm_ftpm_tee: Document fTPM TEE driver (2019-09-02 17:08:35 +0= 300) >> > > >> > > ---------------------------------------------------------------- >> > > tpmdd updates for Linux v5.4 >> > > >> > > ---------------------------------------------------------------- >> > > Jarkko Sakkinen (1): >> > > tpm: Remove a deprecated comments about implicit sysfs locking >> > > >> > > Lukas Bulwahn (1): >> > > MAINTAINERS: fix style in KEYS-TRUSTED entry >> > > >> > > Sasha Levin (2): >> > > tpm/tpm_ftpm_tee: A driver for firmware TPM running inside TEE >> > > tpm/tpm_ftpm_tee: Document fTPM TEE driver >> > > >> > > Stefan Berger (2): >> > > tpm_tis_core: Turn on the TPM before probing IRQ's >> > > tpm_tis_core: Set TPM_CHIP_FLAG_IRQ before probing for interru= pts >> > >> > Hi Jarrko, >> > >> > I'm replying here because I can't find the patches to reply to >> > directly from LKML. >> > >> > Commit 7f064c378e2c "tpm_tis_core: Turn on the TPM before probing >> > IRQ's" in the v5.3-stable tree caused a regression on a pre-release >> > platform with a TPM2 device. The interrupt starts screaming when the >> > driver is loaded and does not stop until the device is force unbond >> > from the driver by: >> > >> > echo IFX0740:00 > /sys/bus/platform/drivers/tpm_tis/unbind >> > >> > I checked v5.4-rc8 and it has the same problem. I tried reverting: >> > >> > 1ea32c83c699 tpm_tis_core: Set TPM_CHIP_FLAG_IRQ before probing for in= terrupts >> > 5b359c7c4372 tpm_tis_core: Turn on the TPM before probing IRQ's >> > >> > Which silenced the screaming interrupt problem, but now the TPM is rep= orting: >> > >> > [ 3.725131] tpm_tis IFX0740:00: 2.0 TPM (device-id 0x1B, rev-id 16) >> > [ 3.725358] tpm tpm0: tpm_try_transmit: send(): error -5 >> > [ 3.725359] tpm tpm0: [Firmware Bug]: TPM interrupt not working, >> > polling instead >> > >> > ...at load, where it was not reporting this previously. Can you take a= look? >> >> It is already in WiP: >> >> https://patchwork.kernel.org/patch/11240111/ >> >> Stefan also sent patches that revert to changes that you described: >> >> https://patchwork.kernel.org/cover/11262363/ >> >> Probably better first to fix the issue on top of master before deciding >> actions. > >... and apologies for late response. > >/Jarkko > There also was that other issue reported on the list about tpm_tis_core_init failing when calling tpm_get_timeouts due to the power gating changes.