linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: Jarkko Sakkinen <jarkko@kernel.org>,
	Matthew Garrett <mjg59@google.com>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	linux-integrity <linux-integrity@vger.kernel.org>
Subject: Re: Recent tpm_tis IRQ handling changes are causing kernel backtraces
Date: Tue, 16 Mar 2021 16:34:01 +0100	[thread overview]
Message-ID: <e4afc566-0114-c5a3-ebda-a775132e999d@redhat.com> (raw)
In-Reply-To: <34442b17-c8e6-9d33-831f-fcbf3a38552b@redhat.com>

Hi,

On 2/11/21 2:09 PM, Hans de Goede wrote:
> Hi Jerry,
> 
> It looks like there still is an issue with the recent changes to the tpm_tis IRQ
> handling. At least I think those are the cause I did not dive any deeper,
> I just noticed that we (Fedora) have been receiving an aweful lot of
> kernel tpm_tis_send_data backtraces with most starting with tpm_tis_probe_irq_...
> 
> See for example:
> https://bugzilla.redhat.com/show_bug.cgi?id=1912167
> https://bugzilla.redhat.com/show_bug.cgi?id=1927610
> 
> Those are just the 3 which landed in my inbox today, for much more see:
> https://bugzilla.redhat.com/buglist.cgi?quicksearch=tpm_tis_send_data
> (this shows 18 bugs atm).
> 
> These were reported through the Fedora ABRT tools which automatically
> collects backtraces, the bugs have links to the ABRT reports, e.g. :
> https://retrace.fedoraproject.org/faf/reports/28155/
> https://retrace.fedoraproject.org/faf/reports/37107/
> 
> The 28155 report says that so far there have been 308,412 (ouch) automatic
> uploads of that particular variant of these backtraces
> 
> Note the second (37107) retrace report is about this happening
> on resume, rather then on probe/tpm_tis_probe_irq_... time.
> 
> Did your work on this work land in 5.10 ? Or could it be that the
> issue is an incomplete backport to the 5.10.y stable series ?

Ping ?

It is raining bug-reports about this:

https://bugzilla.redhat.com/buglist.cgi?quicksearch=tpm_tis_send_data

Currently lists 25 bugs and that is excluding bugs which have already
been marked as a duplicate.

Can someone involved in the patch-series which is causing this regression
please take a look at these kernel backtraces ?

Regards,

Hans


  reply	other threads:[~2021-03-16 15:34 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 13:09 Recent tpm_tis IRQ handling changes are causing kernel backtraces Hans de Goede
2021-03-16 15:34 ` Hans de Goede [this message]
2021-03-16 19:18   ` Jarkko Sakkinen
2021-05-08  9:07     ` Hans de Goede
2021-05-10 17:25       ` Jarkko Sakkinen
2021-05-11  8:37         ` Hans de Goede
2021-05-11 23:48           ` Jarkko Sakkinen
2021-05-26 19:03           ` Hans de Goede
2021-05-27 14:00             ` Jarkko Sakkinen
2021-05-27 15:27               ` Hans de Goede
     [not found]                 ` <20210531043616.u3v25qzkkrik5apq@kernel.org>
2021-05-31  8:24                   ` Hans de Goede
2021-06-01 18:02                     ` Jarkko Sakkinen
2021-06-01 16:04                   ` Hans de Goede
2021-06-01 18:03                     ` Jarkko Sakkinen
2021-06-14 13:33                     ` Hans de Goede
2021-06-15 13:01                       ` Jarkko Sakkinen
2021-06-15 13:59                         ` Hans de Goede
2021-06-23 13:37                           ` Jarkko Sakkinen
2021-06-21 12:04                       ` Hans de Goede
2021-06-23 13:40                         ` Jarkko Sakkinen
2021-06-23 13:54                           ` Hans de Goede
2021-06-29 18:04                             ` Recent tpm_tis IRQ handling changes are causing kernel backtraces] Jarkko Sakkinen
2021-06-29 19:14                               ` Hans de Goede
2021-06-29 22:05                                 ` Jarkko Sakkinen
2021-06-30 12:47                                   ` Hans de Goede
2021-06-30 13:36                                     ` Hans de Goede
2021-07-09 18:44                                       ` Jarkko Sakkinen
2021-07-17 16:10                                         ` Hans de Goede
2021-07-27  2:50                                           ` 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=e4afc566-0114-c5a3-ebda-a775132e999d@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=jarkko@kernel.org \
    --cc=jsnitsel@redhat.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=mjg59@google.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;
as well as URLs for NNTP newsgroup(s).