Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp1158146imm; Fri, 29 Jun 2018 12:26:55 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfQbHhlrSvjXAi4Jgh6ztkWbQftr9RRq0NfjhsqJbkHGETKqhvzSzvEu7h9j6sP/pc7ytUA X-Received: by 2002:a63:b349:: with SMTP id x9-v6mr407215pgt.337.1530300415205; Fri, 29 Jun 2018 12:26:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530300415; cv=none; d=google.com; s=arc-20160816; b=Qq+LZrUtFx0f7Bao4k7Q31X4nvjpvlT4Sn7F/9kqt8m+hshkvo++bNY4zvU9ewduRD 0npmYyG/G0edYC77suHd8cy6M7wjOi29rf6fp4htm8ZVlj7En/Z1lni8VaKSwYyz46i1 te9FuMAxKClPpLZ6qA9bUADwNoO2S8KAuUzTNDXedDsDXSVPa7rH8Z50f5VLst1tisLb W/qFizROdjR7TWMTBGrrDAinyi1sFJuEQ5ykTGY2W2cP4VXwTuazwO8+DtHLLUth1WWR kV8NaLRbyIQtjA6yaLHeG0Fpnl9aD/Wx/8V8lhQs9ikzPxfd4v4luuElRnkkXZ5yexOe bumg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-transfer-encoding :mime-version:references:in-reply-to:date:cc:to:from:subject :arc-authentication-results; bh=1OQEoFNC/+vKDJYTpJKYieaRcBzP8AUn+obpyCZoEoo=; b=h4c8ENP0SoL4T2jv7ijmSU7Dm6HxaxzO12ifYZzo+NcRaU2LuRUIY0ZITg2rNM4Unq 5BdT9iXHlxg9oY+yPympHyY61X7LBGwV6dcM3yD3MAo53J2XKmd+SLPU4iZKuDI0Bj8H hzKfp4RZjRwktS4id99bduzDff4u3Oty+WL+Icdp33/J9zp962uzaFsCKgvsOMEtAMlW rMwiOZn7lOsWzcK4x/pFDLCeLKC4WEH62kXtLyKx3jIsm4FkAzo45Aq8BRsaR5dLxW46 zrkJflFUuj0ScfU5M6YpFng5cZz200kFYu417tV4RyQovzq9FBvPfF7zgB2ZS07Ci5qq fqHw== ARC-Authentication-Results: i=1; mx.google.com; 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=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a128-v6si10169859pfb.81.2018.06.29.12.26.40; Fri, 29 Jun 2018 12:26:55 -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; 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=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755550AbeF2PCO (ORCPT + 99 others); Fri, 29 Jun 2018 11:02:14 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:42874 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753194AbeF2PB6 (ORCPT ); Fri, 29 Jun 2018 11:01:58 -0400 Received: from pps.filterd (m0098410.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w5TExcUM011848 for ; Fri, 29 Jun 2018 11:01:56 -0400 Received: from e06smtp05.uk.ibm.com (e06smtp05.uk.ibm.com [195.75.94.101]) by mx0a-001b2d01.pphosted.com with ESMTP id 2jwmymwxg0-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Fri, 29 Jun 2018 11:01:56 -0400 Received: from localhost by e06smtp05.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 29 Jun 2018 16:01:53 +0100 Received: from b06cxnps3075.portsmouth.uk.ibm.com (9.149.109.195) by e06smtp05.uk.ibm.com (192.168.101.135) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Fri, 29 Jun 2018 16:01:50 +0100 Received: from d06av24.portsmouth.uk.ibm.com (mk.ibm.com [9.149.105.60]) by b06cxnps3075.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w5TF1nKR33226898 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 29 Jun 2018 15:01:49 GMT Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id EF2624204B; Fri, 29 Jun 2018 16:01:37 +0100 (BST) Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 01A1142042; Fri, 29 Jun 2018 16:01:37 +0100 (BST) Received: from localhost.localdomain (unknown [9.80.81.179]) by d06av24.portsmouth.uk.ibm.com (Postfix) with ESMTP; Fri, 29 Jun 2018 16:01:36 +0100 (BST) Subject: Re: [PATCH v7 0/5] Have IMA find and use a tpm_chip until system shutdown From: Mimi Zohar To: Jarkko Sakkinen , Stefan Berger , linux-integrity@vger.kernel.org, James Morris Cc: jgg@ziepe.ca, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org Date: Fri, 29 Jun 2018 11:01:37 -0400 In-Reply-To: <285d705b92b2f3a9351ac31b2e25ad36cb47204a.camel@linux.intel.com> References: <20180626190933.2508821-1-stefanb@linux.vnet.ibm.com> <285d705b92b2f3a9351ac31b2e25ad36cb47204a.camel@linux.intel.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.5 (3.20.5-1.fc24) Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-TM-AS-GCONF: 00 x-cbid: 18062915-0020-0000-0000-000002A156CB X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18062915-0021-0000-0000-000020ED5BAE Message-Id: <1530284497.3366.145.camel@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-06-29_06:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=821 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1806210000 definitions=main-1806290161 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2018-06-29 at 15:13 +0300, Jarkko Sakkinen wrote: > On Tue, 2018-06-26 at 15:09 -0400, Stefan Berger wrote: > > This series of patches converts IMA's usage of the tpm_chip to find a TPM > > chip initially and use it until the machine is shut down. To do this we need > > to introduce a kref for the tpm_chip that IMA and all other users of a > > tpm_chip hold onto until they don't need the TPM chip anymore. > > All the TPM patches are now in my tree and I just updated also the > next branch so they should be soon available also in linux-next. James, do you have a preference?  Should I merge the patches in Jarkko's next branch or just base the integrity branch on top of it? Mimi