[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023060736-immodest-doormat-f957@gregkh>
Date: Wed, 7 Jun 2023 19:49:45 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Lino Sanfilippo <l.sanfilippo@...bus.com>
Cc: Bagas Sanjaya <bagasdotme@...il.com>,
Chris Packham <Chris.Packham@...iedtelesis.co.nz>,
Jarkko Sakkinen <jarkko@...nel.org>,
Sasha Levin <sashal@...nel.org>,
Peter Huewe <peterhuewe@....de>,
Jason Gunthorpe <jgg@...pe.ca>,
Linux Kernel Integrity <linux-integrity@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Regressions <regressions@...ts.linux.dev>,
stable@...r.kernel.org
Subject: Re: New kernel warning after updating from LTS 5.15.110 to 5.15.112
(and 5.15.113)
On Wed, Jun 07, 2023 at 05:47:57PM +0200, Lino Sanfilippo wrote:
>
> Hi Greg,
>
> On 06.06.23 08:45, Greg KH wrote:
> >>
> >> Lino, it looks like this regression is caused by (backported) commit of yours.
> >> Would you like to take a look on it?
> >>
> >> Anyway, telling regzbot:
> >>
> >> #regzbot introduced: 51162b05a44cb5
> >
> > There's some tpm backports to 5.15.y that were suspect and I'll look
> > into reverting them and see if this was one of the ones that was on that
> > list. Give me a few days...
> >
>
> Could you please consider to apply (mainline) commit 0c7e66e5fd69 ("tpm, tpm_tis: Request threaded
> interrupt handler") to 5.15.y?
>
> As Chris confirmed it fixes the regression caused by 51162b05a44cb5 ("tpm, tpm_tis: Claim locality
> before writing interrupt registers").
>
> Commit 0c7e66e5fd69 is also needed for 5.10.y, 6.1.y and 6.3.y.
Now queued up, thanks.
greg k-h
Powered by blists - more mailing lists