Received: by 10.223.185.116 with SMTP id b49csp5392378wrg; Wed, 7 Mar 2018 10:58:37 -0800 (PST) X-Google-Smtp-Source: AG47ELtYUH/Tge0O+I/BCJvxCplxC8e2xBH2ruqRb4oQeGV+OwFzSYHBAEf0n4vF6N0Xvo/G889K X-Received: by 2002:a17:902:c1:: with SMTP id a59-v6mr20874501pla.284.1520449117597; Wed, 07 Mar 2018 10:58:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520449117; cv=none; d=google.com; s=arc-20160816; b=ccmCqdjxUNCHwkMHtsgYbuWAJtVtCp/Up3s0B8Zx7r35w9IZ8DwR6W6wOqy/Rc/uM6 ijnFyh+q/oTVSX0QFa/hOzD7xz7IHOiP61wtN4qDBavyoyrCq5GQMdYZ0ezESvhOrSp7 DraK6lrvuugc4NmfT8QFBU90TBZNlNAm6q4bL0wSYL24TDKeIaQ/jo8or+VdPzDVWNgL KP96abIfdyGAMgB9mOrVKByxuAS4QzkEDPRSFlF4tDt4fCUvXHzZkCL3GuP4HggPeJ2f BJvSjfjcGrJpGn62kbsI15yhn2cgdtoqYxul4dqJXNkH9m05bYn4MOU7xKNykD41/iaK 3DyA== 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=OKqC0qONw0Q4HUWrtYyC9eQeC0glTkKzbOQcqkiF8IU=; b=BlTK2uHqJw+HQEgKJQxgpZfDo6wM2/nIgOtQyTp4BTvEcauuNEPfD/uGwdQqITAKy5 WdwHBQB1h9j3NXaYAdmNFktssymY+KTwpBMQ+xDWY8ICbUQ410/OKTY78dYW+0uUAXmi drZ/UpFFpVHK3yjlsetfF5NX0EezwK6qLchmnGziWZd8EC/xi43GCeprhnh3YX5oE3Yo STHxDj3VABv/FnEdw6jlodqrqQM1GaMMTRThAi+OzsYPYl1U4IlQal+nvsADPSbdScys spkJn2hmnqxqz6TMqSFJMTbwWd6fTfNT6TuBDF0j98YXfhn2XIAEySwx0Xoc2kNypmmK mZVQ== 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 g2-v6si10350505plo.567.2018.03.07.10.58.23; Wed, 07 Mar 2018 10:58:37 -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; 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 S1754620AbeCGS4G (ORCPT + 99 others); Wed, 7 Mar 2018 13:56:06 -0500 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:46498 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754553AbeCGS4D (ORCPT ); Wed, 7 Mar 2018 13:56:03 -0500 Received: from pps.filterd (m0098393.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w27IscNs057399 for ; Wed, 7 Mar 2018 13:56:02 -0500 Received: from e06smtp12.uk.ibm.com (e06smtp12.uk.ibm.com [195.75.94.108]) by mx0a-001b2d01.pphosted.com with ESMTP id 2gjm9kus61-1 (version=TLSv1.2 cipher=AES256-SHA256 bits=256 verify=NOT) for ; Wed, 07 Mar 2018 13:56:02 -0500 Received: from localhost by e06smtp12.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 7 Mar 2018 18:56:00 -0000 Received: from b06cxnps4076.portsmouth.uk.ibm.com (9.149.109.198) by e06smtp12.uk.ibm.com (192.168.101.142) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Wed, 7 Mar 2018 18:55:56 -0000 Received: from d06av25.portsmouth.uk.ibm.com (d06av25.portsmouth.uk.ibm.com [9.149.105.61]) by b06cxnps4076.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w27Ittt438862886; Wed, 7 Mar 2018 18:55:55 GMT Received: from d06av25.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 5377811C050; Wed, 7 Mar 2018 18:48:41 +0000 (GMT) Received: from d06av25.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 0A18811C04C; Wed, 7 Mar 2018 18:48:40 +0000 (GMT) Received: from localhost.localdomain (unknown [9.80.81.183]) by d06av25.portsmouth.uk.ibm.com (Postfix) with ESMTP; Wed, 7 Mar 2018 18:48:39 +0000 (GMT) Subject: Re: [PATCH] security: Fix IMA Kconfig for dependencies on ARM64 From: Mimi Zohar To: Jason Gunthorpe , Jiandi An Cc: dmitry.kasatkin@gmail.com, jmorris@namei.org, serge@hallyn.com, linux-integrity@vger.kernel.org, linux-ima-devel@lists.sourceforge.net, linux-ima-user@lists.sourceforge.net, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org Date: Wed, 07 Mar 2018 13:55:53 -0500 In-Reply-To: <20180307185132.GA30102@ziepe.ca> References: <1520400386-17674-1-git-send-email-anjiandi@codeaurora.org> <20180307185132.GA30102@ziepe.ca> 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: 18030718-0008-0000-0000-000004D90961 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18030718-0009-0000-0000-00001E6C2618 Message-Id: <1520448953.10396.565.camel@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-03-07_09:,, 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 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1803070215 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2018-03-07 at 11:51 -0700, Jason Gunthorpe wrote: > On Tue, Mar 06, 2018 at 11:26:26PM -0600, Jiandi An wrote: > > TPM_CRB driver is the TPM support for ARM64. If it > > is built as module, TPM chip is registered after IMA > > init. tpm_pcr_read() in IMA driver would fail and > > display the following message even though eventually > > there is TPM chip on the system: > > > > ima: No TPM chip found, activating TPM-bypass! (rc=-19) > > > > Fix IMA Kconfig to select TPM_CRB so TPM_CRB driver is > > built in kernel and initializes before IMA driver. > > > > Signed-off-by: Jiandi An > > security/integrity/ima/Kconfig | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/security/integrity/ima/Kconfig b/security/integrity/ima/Kconfig > > index 35ef693..6a8f677 100644 > > +++ b/security/integrity/ima/Kconfig > > @@ -10,6 +10,7 @@ config IMA > > select CRYPTO_HASH_INFO > > select TCG_TPM if HAS_IOMEM && !UML > > select TCG_TIS if TCG_TPM && X86 > > + select TCG_CRB if TCG_TPM && ACPI > > select TCG_IBMVTPM if TCG_TPM && PPC_PSERIES > > help > > The Trusted Computing Group(TCG) runtime Integrity > > This seems really weird, why are any specific TPM drivers linked to > IMA config, we have lots of drivers.. > > I don't think I've ever seen this pattern in Kconfig before? As you've seen by the current discussions, the TPM driver needs to be initialized prior to IMA.  Otherwise IMA goes into TPM-bypass mode.  That implies that the TPM must be builtin to the kernel, and not as a kernel module. Mimi