From: Jarkko Sakkinen <jarkko@kernel.org>
To: Jarkko Sakkinen <jarkko.sakkinen@iki.fi>
Cc: Yuqi Xu <xuyuqiabc@gmail.com>,
linux-integrity@vger.kernel.org, Peter Huewe <peterhuewe@gmx.de>,
Jason Gunthorpe <jgg@ziepe.ca>,
Jerry Snitselaar <jsnitsel@redhat.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
stable@vger.kernel.org, Vega <vega@nebusec.ai>,
Ren Wei <weir@nebusec.ai>,
xuyq21@lenovo.com
Subject: Re: [PATCH v2 1/1] tpm: reject duplicate PCR banks in tpm2_get_pcr_allocation
Date: Tue, 20 Oct 2026 18:30:11 +0300 [thread overview]
Message-ID: <ateJA_WanjASrIUM@kernel.org> (raw)
In-Reply-To: <ar8hhrjQQw_yfghj@iki.fi>
On Fri, Oct 02, 2026 at 06:14:14AM +0300, Jarkko Sakkinen wrote:
> On Wed, Sep 30, 2026 at 11:33:00AM +0800, Yuqi Xu wrote:
> > On Wed, Sep 30, 2026 at 01:34:48AM +0300, Jarkko Sakkinen wrote:
> > > No need to resend a new version but I'd need a link to the *report* to
> > > retain reported-by tag here.
> >
> > https://bugtracker.nebusec.ai/f/675
> >
> > This is the report. The page requires a sign-in or registration
> > before it opens.
>
> For me this is good enough given that there is nothing unclear in the
> bug fix itself.
>
> Thanks.
OK, so now that I was writing summary of TPM pull request changes, I
came into conclusion that this is not a bug fix, unless you can show
from TCG specifications that this is possible spec allowed behaviour.
So I can keep the commit but would remove fixes and bug related tags
from this. It is essentially hardening and safety measure but not a
bug fix.
Do you have something to say that I might have missed?
Br, Jarkko
prev parent reply other threads:[~2026-10-20 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 8:26 [PATCH v2 0/1] tpm: reject duplicate PCR banks in tpm2_get_pcr_allocation Yuqi Xu
2026-09-28 8:27 ` [PATCH v2 1/1] " Yuqi Xu
2026-09-29 21:25 ` Jarkko Sakkinen
2026-09-29 22:34 ` Jarkko Sakkinen
2026-09-30 3:33 ` Yuqi Xu
2026-09-30 6:30 ` Yuan Tan
2026-10-02 3:14 ` Jarkko Sakkinen
2026-10-20 15:30 ` Jarkko Sakkinen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ateJA_WanjASrIUM@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=jarkko.sakkinen@iki.fi \
--cc=jgg@ziepe.ca \
--cc=jsnitsel@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=stable@vger.kernel.org \
--cc=vega@nebusec.ai \
--cc=weir@nebusec.ai \
--cc=xuyq21@lenovo.com \
--cc=xuyuqiabc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox