From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=209.85.128.48 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1792666484; b=M5QRBard+2TQ47t/Ryd6yqxGEq47XHbmBCRFsC67//ANEIPK3TCtm1DTmQDg/q/MVLHt mMvUCUt3jf1kBnPYT/mtKA2Vt8IT9Z0OTeWCIrZfSYDJLPYWRqwrjxwUFg6WsEsB/Ke0i 23cy8QxZvkhrNroHh/imyo9C4KkKkn6xKhSHSwPtdf51GAGLphAAjDF4QsW2Vgzrc+1zV YwnpZzFnu7yyFtA3LZufXTPB3lYsMK600Ld55IWnx5DB1OJ15qiTiqCmA/BAPPd8QDc92 fz3DcDlCO51b1PNNoJTogW9/dk1pA+kRpf1P7x7fBz44otmQSV0xGkFnDii1SVAsvKA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1792666484; h=DMARC-Filter:Received:DKIM-Signature:X-Google-DKIM-Signature: X-Forwarded-Encrypted:X-Gm-Message-State:X-Gm-Gg:X-Received:Received: Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; bh=wsdeMYd/7eLXCr9Ufg4dZ6+EW6LYxWJjZpkMLdZ1OLI=; b=TigtjVHPdwvN600TARKvW3uxVd3iRupYCUUP4+4DLM3eTFW7ldeBM3LniOWQ7GeKgZYP jGcBQsVBoiyjoKvep6F/AmCQ7aC0MynwElow3mnSCPNZXPUzz/W142hl6Il80mIFW174N XXfsLLCH7UhVfBOJx+fy9nQgf73NoCM0ppIr8/QQ21c8RqGjvIsp4apYMRqmRlJoJWQ9x UgAS/CBAEEuYH/fNDjDm1jbmQ/TpD7AaMUTQ+usGRrxoe21BSdI6UH7LDHIKxiCNCOMkq 6yhi/y1+MvVEzNpU3iziMg4LJyj2MgR6ftt1H6ML9Jj4o3iJO61kbiFmmd3ZwEz553g== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=resnulli.us; spf=pass smtp.mailfrom=resnulli.us; dkim=pass header.d=resnulli.us header.i=@resnulli.us header.a=rsa-sha256 header.s=google header.b=iVzM+4Wh; arc=none smtp.remote-ip=209.85.128.48 Received: from mail-wm1-f48.google.com (mail-wm1-f48.google.com [209.85.128.48]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 08B3E606A325 for ; Thu, 22 Oct 2026 10:54:37 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 08B3E606A325 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=resnulli.us Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=resnulli.us Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key, unprotected) header.d=resnulli.us header.i=@resnulli.us header.a=rsa-sha256 header.s=google header.b=iVzM+4Wh Received: by mail-wm1-f48.google.com with SMTP id 5b1f17b1804b1-4a140e7405dso14547195e9.3 for ; Thu, 22 Oct 2026 03:54:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=resnulli.us; s=google; t=1792666476; x=1793271276; darn=vger.kernel.org; h=in-reply-to:content-disposition:content-type:mime-version :references:message-id:subject:cc:to:from:date:from:to:cc:subject :date:message-id:reply-to:content-type; bh=wsdeMYd/7eLXCr9Ufg4dZ6+EW6LYxWJjZpkMLdZ1OLI=; b=iVzM+4Wh7gDZgzymw32x+37naO3wz4NgCsioUd0xXmmYJLxHde730j8vwEBFHOigDt spQz+0mFByaQFwaDUr0c2ae1SeHnkPpIIUiMHP/cu/tOLU497pMtVgSh3Oe97yRxau59 1+aFiEk/doEVxAUQ4uQi5J3n037VefaeLSYfEBVYI0ezdQtHblQfteC+MpB14t0Yb02b crjq4VN8tYFrfN5YMd66+KGrNKNSCqW3QnCUx8AtGlqCodiHQpo5792+KihYy5FXZLYH ZumXm9uvYooJDFh1wBcflp8vYOWr5d2vJQZRxljy7S6k5IwMbVTRod9BghghqnSJwFlZ satA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1792666476; x=1793271276; h=in-reply-to:content-disposition:content-type:mime-version :references:message-id:subject:cc:to:from:date:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=wsdeMYd/7eLXCr9Ufg4dZ6+EW6LYxWJjZpkMLdZ1OLI=; b=KSYG2uvpJUnEOATNLUAs5k6y1Q4s7mle4D1vNp26ZVF5vU+nrsb+XIdKYQK0N5Yiuy v1f82PAaqjovq6lrntVTfTqygBnuXgnDYoKQnZp46MC7i3gGs2SA56B8ezC6QZMz+LE2 qzyohxps3lLVdmOBxawOCp3gqps4aMWEq5mmJ73zfVee+GSHpKHNY0+R22BUyLYGRknI 0tS/vC61Cv/GrB/6JRWXLBXkdEmaEMVwbb4CRUbEwnzT46f+HXz1RVWhdIrFEiOmdncS JZuoS7f6FvKpSDbdGp+gHGoHQ7xmxeyq8aiUHa+6ilTN/WEh6zovR+Rx9HAKeEXZV4Lp mEnw== X-Forwarded-Encrypted: i=1; AKwUvBylYkqkwRGgFiaqCmXbTIFRr0vAn5aHtwle1rRWPwK1iXI+XIty5wxM5KXj5lS+1yxxA4g=@vger.kernel.org X-Gm-Message-State: AFq9FYJq5/b6/wwSf6NLnnLrnbAVOgybTR6XaHy8MiLk8WUurP/hIKnD v6rLMgUKeggpAYlMXyCs9LZwOo8HwfDrZ6/7CgAHX4iI2UV0AuydmD6LbPPZzArwKm0= X-Gm-Gg: AYBFou3gbKqCePkkBUoOpH1LitsBhtLb2E2Yy+rYBRX61dEeSubaxWVPNdNSIvdIi/n P3li43Hsa7xYVARuLsWEorrez4M5nUZYFhqc6rpRxT1OQV9NdhYP7hUhWTYtsXfCpQU5uO9RQ+t YcmOtJ1tYYHEcqPfd905vUJXaAggTyz8aNz+6ZRdT6vFb9PDVQilMU6JzxhHO1530Fztjtf7N85 iQ36qwNLaxOCN/UXD461M3rgBVc35Udlyf2Cqa/R8bg6rCoECWpg7hEdyQAuY+6mwyP6FW65ano VSVjbBg48oYvmsK8m+ZWNFDxFq7mjraTsUR1gkLb2u3PWB2GhlxA24DW6yfzUe2WyOvkqixQ86y 5zCG65Chgf8Zf1yRvB8aUR00mmPq3t4aqrUSRm2ql/a4vn+9E8opFnBWc1bNbmqZE9//7Ph2EEe lk/b/IAvIt3lgzmj+dEIVNV3FjY27PoyJUc8CdjvtkSng+whRddHbLWsAW/haXq7gie0tvInYQq QezIG7CDedwgmV8cidmAhialx1SFUGq6dU1wBqBmpORAqOrBRv1znSR3HhQDeN09M0= X-Received: by 2002:a05:6000:288e:b0:485:8cc8:1f5f with SMTP id ffacd0b85a97d-48e264a1f81mr10449260f8f.42.1792666476063; Thu, 22 Oct 2026 03:54:36 -0700 (PDT) Received: from localhost ([140.209.217.211]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-48e2583522esm11890881f8f.35.2026.10.22.03.54.35 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 22 Oct 2026 03:54:35 -0700 (PDT) Date: Thu, 22 Oct 2026 12:54:30 +0200 From: Jiri Pirko To: Mimi Zohar Cc: Jason Gunthorpe , Dionna Glaze , Jarkko Sakkinen , linux-coco@lists.linux.dev, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, x86@kernel.org, kvm@vger.kernel.org, linux-doc@vger.kernel.org, david.quigley@intel.com, lukas@wunner.de, ksinyuk@kernel.org, rodrigo.vivi@intel.com, cedric.xing@intel.com, sameo@meta.com, James.Bottomley@hansenpartnership.com, aik@amd.com, jpiotrowski@nvidia.com, qinkun@google.com, pgonda@google.com, jic23@kernel.org, alistair.francis@wdc.com, ankita@nvidia.com, suzuki.poulose@arm.com, kas@kernel.org, rick.p.edgecombe@intel.com, elena.reshetova@intel.com, dave.hansen@linux.intel.com, sathyanarayanan.kuppuswamy@linux.intel.com, peter.fang@intel.com, roberto.sassu@huawei.com Subject: Re: [PATCH RFC 00/20] attestation: Add a common subsystem and TDX support Message-ID: References: <20261017231007.GP13920@nvidia.com> <20261019225658.GS13920@nvidia.com> <103486a4a29ecc7b72940dd051c00ae59266bd05.camel@linux.ibm.com> <20261021143529.GP3008132@nvidia.com> <8d8833fac61558a94af415143530884349584a2f.camel@linux.ibm.com> X-Mailing-List: kvm@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8d8833fac61558a94af415143530884349584a2f.camel@linux.ibm.com> Wed, Oct 21, 2026 at 09:05:09PM +0200, zohar@linux.ibm.com wrote: >On Wed, 2026-10-21 at 11:35 -0300, Jason Gunthorpe wrote: >> On Wed, Oct 21, 2026 at 10:12:34AM -0400, Mimi Zohar wrote: >> > > > I think for now we should not include a new dynamic log here, the uAPI >> > > > around this Jiri drafted can remain a future step. I don't want to >> > > > open complicated discussions about new functionality at this >> > > > stage. The whole CTLV idea in general is a big enough thing to bite >> > > > off for this series. >> > > >> > > Okay, dropping the log from this set. >> > >> > Thank you. Please keep in mind going forward, that the scarce hardware register >> > limitation (like the 4 TDX RTMRs) should be resolved (e.g. by multiplexing the >> > extension path), not by combining distinct measurement lists. >> >> I'm not sure what you mean? >> >> Since the HW doesn't support sealing the only *technical* requirement >> is the verifier can reproduce the measurement register hash. So long >> as we can get there we can do whatever. >> >> Multiplexing extension alone isn't enough. We need some scheme to >> reconstruct interleaved logs too. >> >> For example we could add an atomic sequence number for each >> extend. Every log sharing a register can report the sequence >> number. The verifier would have to globally sort all logs to confirm >> the hash. >> >> Hopefully we don't have to tackle this problem. I hope that 4 >> registers is enough for Linux. One for IMA, one for systemd, one for >> user? Plus a spare! > >Agreed, I hope you don't have to tackle it either. > >> >> Maybe we can build a multiplexed scheme on the spare? I don't know. > >To avoid interleaving the logs, AI had suggested multiplexing or virtualization >of the RTMRs. Whether is has any merit, I'll leave to you. Here's the very >short AI explanation: > >"Instead of allowing external drivers or subsystems to execute a direct, raw >extend command to a specific hardware register index, the new attestation >subsystem should act as a Hypervisor for Registers." Isn't the hypervisor what we are doing now? I mean multiple extension originators share the same register and eventually the same log. Or do you suggest to go even further having a "generic_registerX" exposed for every hw implementation allowing the user to have full abstraction? The "generic_registerX" would be always alias to something hw specific, like RTMR2 for example of TDX. > >> >> But we almost certainly need to have logs sequentially created in time >> occupying the same register. Ie IMA may take over the register from >> UEFI logging. Here we'd want to report the start/end hash values of >> the logs back to userspace so the verifier can stitch the order back >> together. >> >> It would also be nice to think about a way to restrict the registers >> to help avoid multi-user conflicts from misconfiguration. > >That would definitely be a plus. > >Mimi