linux-kernel - Re: [PATCH v5 4/4] tpm/tpm_svsm: support TPM_CHIP_FLAG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAGxU2F5zQJR4GvZ9ovtQBqMFGs-wBMoCRks=JYQ1JF6qMKK-6g@mail.gmail.com>
Date: Thu, 22 May 2025 10:26:34 +0200
From: Stefano Garzarella <sgarzare@...hat.com>
To: Jarkko Sakkinen <jarkko@...nel.org>
Cc: linuxppc-dev@...ts.ozlabs.org, Peter Huewe <peterhuewe@....de>, 
	Jens Wiklander <jens.wiklander@...aro.org>, linux-integrity@...r.kernel.org, 
	Alexandre Belloni <alexandre.belloni@...tlin.com>, linux-arm-kernel@...ts.infradead.org, 
	Nicolas Ferre <nicolas.ferre@...rochip.com>, Nicholas Piggin <npiggin@...il.com>, 
	Sumit Garg <sumit.garg@...nel.org>, 
	James Bottomley <James.Bottomley@...senpartnership.com>, 
	Claudiu Beznea <claudiu.beznea@...on.dev>, Madhavan Srinivasan <maddy@...ux.ibm.com>, 
	Jason Gunthorpe <jgg@...pe.ca>, linux-kernel@...r.kernel.org, 
	Christophe Leroy <christophe.leroy@...roup.eu>, Naveen N Rao <naveen@...nel.org>, 
	Michael Ellerman <mpe@...erman.id.au>
Subject: Re: [PATCH v5 4/4] tpm/tpm_svsm: support TPM_CHIP_FLAG_SYNC

On Wed, 21 May 2025 at 18:42, Jarkko Sakkinen <jarkko@...nel.org> wrote:
>
> On Wed, May 21, 2025 at 01:12:20PM +0300, Jarkko Sakkinen wrote:
> > > I tried, but the last patch (this one) is based on the series merged
> > > on the tip tree, where I introduced tpm_svsm.
> > > I can see that series in linux-next merged with commit
> > > 16a56ee59ab8ee05e67de35bbb5782ef9cfb4f07,
> > > but I can't see it in your next tree [1].
> > >
> > > How do we proceed in such cases?
> > >
> > > Just to be sure, did I use the right tree?
> >
> > Thanks for the remark. Lemme check tonight. Hold on doing
> > anything ;-) We'll get there...
>
> I just rebased my branches on top of latest from Linus. That is what I
> need base PR also on, and:
>
> $ git show 16a56ee59ab8ee05e67de35bbb5782ef9cfb4f07
> fatal: bad object 16a56ee59ab8ee05e67de35bbb5782ef9cfb4f07
>
> I'd use git cherry-pick on a range to take them from linux-next to a
> mainline tip...

I see, let me know if I can help in some way.

We can also wait the next cycle if it simplifies your work, definitely
no rush on my side.

Thanks,
Stefano