Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp491262ybc; Fri, 22 Nov 2019 08:21:05 -0800 (PST) X-Google-Smtp-Source: APXvYqzPIOpgyI+T5z3PP9u5g9Lo0AlPsZWqjbLSZGhD9O9bdRsXC7Fv86PtJ5ADfbNiVNNOGYSX X-Received: by 2002:a50:8859:: with SMTP id c25mr2069576edc.253.1574439665300; Fri, 22 Nov 2019 08:21:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574439665; cv=none; d=google.com; s=arc-20160816; b=IyJzhlRPX8lUdt9Nx8eG32GqwarQ9NcJb8oA+VkfOtQaEoX/W6X2z0fr0/7/ltInBU AYTl3ey2Qp15aymZUIEpIyywyI8VIsxRRFick+RoWfKGFOMac6aTIfOGJfebaMrxZSqr HGW13m4vNdlcxUG5jsBYPXIRcgMRNa0fA6Qu80imi1B0WwpcYTSsGjZgaoZPqGPNA8w4 TlwAh1Slv+w63vmBKfzEG+KbchLX0wWfvcT2sGn+mlyYFTNs7o5DjHfiEJ+iOTZvSVdL yhu9HX0CGsZ6WLsbvt9OOnsyRX85wrCG35DdnidaM+nkKf1ofXqMJG4DTbIosAPRyO7M rUoQ== 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=ENffYn5INttrwveCQGty9euWtF1hMlls+aNPcfjNNGY=; b=ePXQAJ4MtYlDAfiGJr1n+zCbVRH9HtqJF9q/txSjqpLhDz1C2zphrzgdUY8TSbrQAW Nv/IrT5QQKLFmfBNtF2i7klEXKM/iL3w40isXIp52r0g8OFhLQSAefQNcYMFqUifsUmG xo0xS8M7yITgEs+YYuAGvbpAU7TL0/g3TSB4R1nAm22uUjGsS0+P+SqiDEgCSp7kAul0 5+FIr+2KoRhcTigzrQ+saXNyv9CYBQwoI1D8pzfgiujYoA+OOsiF/qxMT2WwUecDfeeJ 4J8EEAVIfnfQryfgwq4FhlEFS3rrYJVRKeJZYPkB9Nhbtgdy/wfnV243IMFN7wJrHOMV pVEQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="WENB39G/"; 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 v10si5590231edc.62.2019.11.22.08.20.40; Fri, 22 Nov 2019 08:21:05 -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="WENB39G/"; 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 S1727484AbfKVQSn (ORCPT + 99 others); Fri, 22 Nov 2019 11:18:43 -0500 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:59401 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727472AbfKVQSn (ORCPT ); Fri, 22 Nov 2019 11:18:43 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1574439521; 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=ENffYn5INttrwveCQGty9euWtF1hMlls+aNPcfjNNGY=; b=WENB39G/sGJDbhGC+0w/UCewzAzT39UK91a0HSHAYeaSvglilxKvTlQlwgJ+qR9p+Jw3ew fZZYNGwAQdc2Ch5g8ktVhuzvSwOad7wxv/SofA2LNwou3MWL2VOBStwTSAbeC9r8RxxaKn A+YKX603AV8ajtRLRmXr7wTWrbfQ3cI= Received: from mail-pj1-f70.google.com (mail-pj1-f70.google.com [209.85.216.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-375-hbivx4yTPtSdbUUPNcVZ2g-1; Fri, 22 Nov 2019 11:18:40 -0500 Received: by mail-pj1-f70.google.com with SMTP id z24so3199083pjt.19 for ; Fri, 22 Nov 2019 08:18:39 -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=jyu3bPky/B7E4tms6aRjpp2QjMTmF1mpdf8LouFgjf4=; b=eNlMJYiHotl/bKViBeBWDjLtr5acxYKh5gtIFu42yza7qZLV5CMNPdR3B1Xu199Yn2 QdYe5QZzNoLWPLfI65xxZ1/fxp5VCXhjV2vIx7aUl2rMcHt3Doc17+YWJN96h06KHuua 2+4vbdBfP2BoY0FoZFZb0wVx6Y833KsDjTYjr9hTMoaRQKAozZ8O2sWtPPczyGCu0PGc HTbw5GvSkJ0DQrhtzsq99I+L4euLx3pdK5kyBCiDq7bSdaMITVMTY4g5iZFdba0yT75H HMTP+8G6EuEwGlxzKCyKW4SCqi+TISnscww06NzDN3Al3QaDqmTrNNcCJQzQ39IH2pcJ vJtw== X-Gm-Message-State: APjAAAVr71JkNWx/W4cG5txgtvLpg0OsLPaEdJFpLDeRNS6ydT3rGy72 OHIFXQtooU99zmB/gDueApn/D0KCBOTp92f1rJvjKJz2gX9qLVcGyR4g8ikbAD852Jx/p+dIWSx EazNK3Sh/lkkFLWPNlja1f5P/ X-Received: by 2002:a63:4a50:: with SMTP id j16mr17254391pgl.308.1574439518928; Fri, 22 Nov 2019 08:18:38 -0800 (PST) X-Received: by 2002:a63:4a50:: with SMTP id j16mr17254356pgl.308.1574439518546; Fri, 22 Nov 2019 08:18:38 -0800 (PST) Received: from localhost (ip70-163-223-149.ph.ph.cox.net. [70.163.223.149]) by smtp.gmail.com with ESMTPSA id x2sm8019786pfn.167.2019.11.22.08.18.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Nov 2019 08:18:37 -0800 (PST) Date: Fri, 22 Nov 2019 09:18:36 -0700 From: Jerry Snitselaar To: Dan Williams Cc: Jarkko Sakkinen , 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: <20191122161836.ry3cbon2iy22ftoc@cantor> Reply-To: Jerry Snitselaar Mail-Followup-To: Dan Williams , Jarkko Sakkinen , Linus Torvalds , Linux Kernel Mailing List , linux-integrity@vger.kernel.org, James Morris , Stefan Berger , stable References: <20190902143121.pjnykevzlajlcrh6@linux.intel.com> MIME-Version: 1.0 In-Reply-To: X-MC-Unique: hbivx4yTPtSdbUUPNcVZ2g-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 On Wed Nov 20 19, 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 8fb8e9e46261e0117cb3cffb6dd8bb7e08f86= 49b: >> >> 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-2019= 0902 >> >> for you to fetch changes up to e8bd417aab0c72bfb54465596b16085702ba0405: >> >> tpm/tpm_ftpm_tee: Document fTPM TEE driver (2019-09-02 17:08:35 +0300) >> >> ---------------------------------------------------------------- >> 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 interrupts > >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 interr= upts >5b359c7c4372 tpm_tis_core: Turn on the TPM before probing IRQ's > >Which silenced the screaming interrupt problem, but now the TPM is reporti= ng: > >[ 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 loo= k? > We've had an issue reported for a Lenovo t490s getting an interrupt storm with the Fedora 5.3 stable kernel, so it appears to be impacting a number o= f systems.