From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id AA57CC3065C for ; Wed, 3 Jul 2024 01:00:55 +0000 (UTC) Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=sbWxUkCl; dkim-atps=neutral Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4WDM0Q2PTfz3cdn for ; Wed, 3 Jul 2024 11:00:54 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dmarc=pass (p=none dis=none) header.from=kernel.org Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=sbWxUkCl; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=kernel.org (client-ip=139.178.84.217; helo=dfw.source.kernel.org; envelope-from=jarkko@kernel.org; receiver=lists.ozlabs.org) Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4WDLzd4XCwz3bbW for ; Wed, 3 Jul 2024 11:00:13 +1000 (AEST) Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 3113D61F7B; Wed, 3 Jul 2024 01:00:11 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 41ECFC116B1; Wed, 3 Jul 2024 01:00:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1719968410; bh=lFjYUrOF7VxhaDL6M2zQYg/d02i9zQFo7I3m20cFD2g=; h=Date:Cc:Subject:From:To:References:In-Reply-To:From; b=sbWxUkCl1dM3JNyZi5jytbVt6B9yMS0pJ63BT+ZfxKLVM0TZEqxdVEkQuONE+UJqB +uRxZpd/QyF2zzT1cENI36TkIi4EzZl/bLY1+9aHkuL/AH2wChOJF8GFj5kcVx2ypv 2BFdkSJsMtxVBrVeWq8rDiLEzVlsUk9R58R/ih9N9wUFJUHD4bpPlmskwMSdNrsPbi +xBIj8tgmC6CdYB7ACpD73k4Ccm4k0DsdV/tT839nsKKxauxOTok+vnnlc8OHJPhDi NsMhjiQ1bckpSpKOcuacVAzaMdvroNnQsBiAoMcW8aIbhm5HI4rsEjwjzodp4UJyma slYJ9ruaQuP5A== Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Wed, 03 Jul 2024 04:00:07 +0300 Message-Id: Subject: Re: [PATCH] tpm: ibmvtpm: Call tpm2_sessions_init() to initialize session support From: "Jarkko Sakkinen" To: "Jarkko Sakkinen" , "Jarkko Sakkinen" , "Stefan Berger" , "Linux regressions mailing list" X-Mailer: aerc 0.17.0 References: <20240617193408.1234365-1-stefanb@linux.ibm.com> <9e167f3e-cd81-45ab-bd34-939f516b05a4@linux.ibm.com> <55e8331d-4682-40df-9a1b-8a08dc5f6409@leemhuis.info> <9f86a167074d9b522311715c567f1c19b88e3ad4.camel@kernel.org> <53d96a8b-26ef-46a3-9b68-3d791613e47c@linux.ibm.com> <85f882ff079554c41a73d8ad4275072c5229f716.camel@iki.fi> In-Reply-To: X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: naveen.n.rao@linux.ibm.com, linux-integrity@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Wed Jul 3, 2024 at 3:48 AM EEST, Jarkko Sakkinen wrote: > On Wed Jul 3, 2024 at 3:34 AM EEST, Jarkko Sakkinen wrote: > > https://lore.kernel.org/linux-integrity/20240703003033.19057-1-jarkko@k= ernel.org/T/#u > > > > There's also bunch of other drivers than tpm_ibmvtpm so better > > to limit it to known good drivers. > > > > I can take at the actual issue in August and will review any > > possible patches then. This one I'll send after my current PR > > for TPM has been merged. > > After this patch has been merged to mainline, you can send your change > as a feature patch for tpm_ibmvtpm and replace Kconfig line with > "depends on ... || TCG_IBMVTPM". > > This zeros the risk other drivers than tpm_tis, tpm_crb and tpm_ibmvtpm, > and thus is the only possible solution that I'm willing to accept in > *fast phase*". I.e. the most conservative and guaranteed route, like > anyone with sane mind should really. Ouch, that won't obviously work so please ignore this! :-) Sorry. It really needs to be !TCG_IBMVTPM because otherwise TCG_TIS_CORE or TCG_CRB would leak the code over there. BR, Jarkko