Received: by 2002:a19:f614:0:0:0:0:0 with SMTP id x20csp26099lfe; Fri, 15 Apr 2022 17:47:22 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxKHs746qiXtrWEy5O3P3hc+zNAIK4y7oIc4JMCsT5Byx5lBMwZYUhLc+TuppN5G+Tez53m X-Received: by 2002:a17:90b:1b4f:b0:1cd:42bd:3bb4 with SMTP id nv15-20020a17090b1b4f00b001cd42bd3bb4mr6851272pjb.226.1650070041851; Fri, 15 Apr 2022 17:47:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1650070041; cv=none; d=google.com; s=arc-20160816; b=mmz4AmKwDG9D89fHXb0uvL5x5yyAnS40+okdqbRtewAOAhL2n5TK7h0NNEEfW6nI3S Q5S/uHK05MMGvxN3uFQ8Tom+7qwzKw6k+5TmO7Xg9HYtbpW2kGWAA2eEd6zH0nSwFSjj TWcDjTPCFOobK5VZhenFk+RIKK84/hd+lwq15wokgZUPOhkKstjJkBR2Lj/Pf+vjd4yj BCwq94AaYOedL8PdTfg1dDqC6nEKGo2nTvkuerkj4LY9bftzEWUyexY3CC2SH4nTXTfq hHeplHL41LjTZmAhlP1S+CB9yqidnpoROt7tl84W539uT/nyZqsjpBx838KE/yTZOEQn KKUw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=59/TGIFeHhYGw/Bdo77/DlhQuTlr43RSGt/+w4gNcdU=; b=SyVdtLql7Sq+AO4WINQzhR+7c/+GL5Gt57LhTM2vYzQb5Ac5gjWtavAc89ctG5jFZX I3JwBNyNT0PQn77WrUW6KOIokwVzMdBpz5V2PNlsXbFr4HpKbwpG7K0y4lO9e92F3m07 u2ltisuaweZwqvmqfgE1owutd68S6wev571ZVXO9gJRccIn4CDzke0QQvO9vABgSfhSR tr2PtiBjEO44F6WX+xRT+avZ8Y12rPHY6F5+bVmdCagtt8bY50FPy/K7FHz8JQMlYFVY uo0uaapFJIemTtulVm45hrBcjjA6I5WE7A0O5IWnhzG6Gq1SBVi6MC2J1MGwbZPAiKTE BLQA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=rhIklwqG; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id p21-20020a62ab15000000b005082e81fc41si2673888pff.146.2022.04.15.17.47.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 15 Apr 2022 17:47:21 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=rhIklwqG; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 951533B2AB; Fri, 15 Apr 2022 17:38:27 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242691AbiDNMQ6 (ORCPT + 99 others); Thu, 14 Apr 2022 08:16:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50536 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232670AbiDNMQ4 (ORCPT ); Thu, 14 Apr 2022 08:16:56 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E76653881; Thu, 14 Apr 2022 05:14:30 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 9AA44B82934; Thu, 14 Apr 2022 12:14:29 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id E23C5C385A1; Thu, 14 Apr 2022 12:14:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1649938468; bh=/lJMbuqCUvWBZpDnchq4yA5y4o3tnZsGQzcMlBudlhc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=rhIklwqG0vK08DiwAvIq46xKLUt/JvMV2fvNoRox7yLjyIuBlgwssXE0jQyTaduf4 Fj1e02mps6gNkaGfUaj6v6PTuxnFMAMwKHAbjPKt/VLqfruZ7oE+jWVgGRnwbXpShI Er/kXcujqDv91ZI+JRntMtLeZs9O8AJ9oz7sObp8FOZQlwldfJB6UvKiS0YuDf2SuH G7l84ppQyR0cUJQTn2PipFZABkvqO0PJbcumc01QZDk28aybHtHipO6xZxUPSyPP4i SDplQYQAFZdiFIEQsMO6jQaW05ZjpLSZPQJBYZQrL5HWN9CwvWJUa4ZhKHP2dGSTqw 3fnzX95jTG8LA== Date: Thu, 14 Apr 2022 15:13:20 +0300 From: Jarkko Sakkinen To: Jason Gunthorpe Cc: Lukas Wunner , Lino Sanfilippo , peterhuewe@gmx.de, devicetree@vger.kernel.org, linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org, stefanb@linux.ibm.com, p.rosenberger@kunbus.com Subject: Re: [PATCH 1/5] tpm: add functions to set and unset the tpm chips reset state Message-ID: References: <20220407111849.5676-1-LinoSanfilippo@gmx.de> <20220407111849.5676-2-LinoSanfilippo@gmx.de> <20220407142526.GW64706@ziepe.ca> <20220410171123.GA24453@wunner.de> <20220411114741.GA64706@ziepe.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220411114741.GA64706@ziepe.ca> X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,MAILING_LIST_MULTI, RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 11, 2022 at 08:47:41AM -0300, Jason Gunthorpe wrote: > On Sun, Apr 10, 2022 at 07:11:23PM +0200, Lukas Wunner wrote: > > On Thu, Apr 07, 2022 at 11:25:26AM -0300, Jason Gunthorpe wrote: > > > On Thu, Apr 07, 2022 at 01:18:45PM +0200, Lino Sanfilippo wrote: > > > > Currently it is not possible to set the tpm chips reset state from within > > > > the driver. This is problematic if the chip is still in reset after the > > > > system comes up. This may e.g. happen if the reset line is pulled into > > > > reset state by a pin configuration in the device tree. > > > > > > This kind of system is badly misdesigned. > > > > > > TPM PCRs fundementally cannot work if the TPM reset line is under > > > software control. > > > > Not every system which incorporates a TPM wants to use or is even capable > > of measuring software state of any kind or perform secure boot. > > > > Those systems may merely want to use the TPM to store key material. > > Then maybe the TPM driver should make it clear somehow that the PCRs > don't work in these systems. > > It is really dangerous to add capabilities like this that should > never, ever be used in sanely designed systems. > > Jason I agree. That niche should do the bad things with oot patches. BR, Jarkko