From: Greg KH <gregkh@linuxfoundation.org>
To: Lino Sanfilippo <l.sanfilippo@kunbus.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
Jarkko Sakkinen <jarkko@kernel.org>,
Sasha Levin <sashal@kernel.org>, Peter Huewe <peterhuewe@gmx.de>,
Jason Gunthorpe <jgg@ziepe.ca>,
Linux Kernel Integrity <linux-integrity@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
stable@vger.kernel.org
Subject: Re: New kernel warning after updating from LTS 5.15.110 to 5.15.112 (and 5.15.113)
Date: Wed, 7 Jun 2023 19:49:45 +0200 [thread overview]
Message-ID: <2023060736-immodest-doormat-f957@gregkh> (raw)
In-Reply-To: <ac5b76af-87dc-b04d-6035-8eda8ba5ed12@kunbus.com>
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
next prev parent reply other threads:[~2023-06-07 17:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 23:42 New kernel warning after updating from LTS 5.15.110 to 5.15.112 (and 5.15.113) Chris Packham
2023-05-29 2:04 ` Bagas Sanjaya
2023-05-29 2:37 ` Chris Packham
2023-06-02 4:10 ` Bagas Sanjaya
2023-06-02 4:19 ` Chris Packham
2023-06-06 1:41 ` Chris Packham
2023-06-06 2:00 ` Bagas Sanjaya
2023-06-06 6:45 ` Greg KH
2023-06-07 15:47 ` Lino Sanfilippo
2023-06-07 17:49 ` Greg KH [this message]
2023-06-20 12:41 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-08-31 9:18 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-06-07 1:43 ` Lino Sanfilippo
2023-06-07 3:23 ` Chris Packham
2023-06-07 15:01 ` Lino Sanfilippo
2023-06-06 9:39 ` Jarkko Sakkinen
2023-06-06 21:04 ` Chris Packham
2023-06-07 16:15 ` Jarkko Sakkinen
[not found] ` <CT7DAF9JJ4KD.37K8GDWP7GKG1@suppilovahvero>
2023-06-08 20:39 ` Chris Packham
2023-06-09 6:20 ` Jarkko Sakkinen
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=2023060736-immodest-doormat-f957@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=bagasdotme@gmail.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=l.sanfilippo@kunbus.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).