From: Stefan Berger <stefanb@linux.ibm.com>
To: Jarkko Sakkinen <jarkko@kernel.org>,
Christian Heusel <christian@heusel.eu>
Cc: Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: [REGRESSION][BISECTED] tpm: Popping noise in USB headphones since 1b6d7f9eb150
Date: Mon, 2 Dec 2024 17:15:16 -0500 [thread overview]
Message-ID: <ce7fa562-7cb7-4adc-934a-560b94ce44f0@linux.ibm.com> (raw)
In-Reply-To: <D5Z62H0XCOQM.J4V5ZDH9E7C7@kernel.org>
On 11/29/24 9:44 PM, Jarkko Sakkinen wrote:
> On Tue Nov 26, 2024 at 1:42 PM EET, Christian Heusel wrote:
>> On 24/10/25 05:47PM, Jarkko Sakkinen wrote:
>>> Yeah, this is on the list.
>>>
>>> See: https://bugzilla.kernel.org/show_bug.cgi?id=219383#c5
>>>
>>> I had a fix for the AMD boot-time issue already over a month ago
>>> but unfortunately took time to get enough feedback.
>>>
>>> BR, Jarkko
>>
>> I'm not sure if this is supposed to be fixed, but AFAIK we hoped that
>> the patchset that was mentioned in bugzilla also helped this issue.
>>
>> The reporter said that the bug is still present in 6.12.1, so this might
>> need further poking 🤔
>
> I'd suggest a workaround for the time being.
>
> In 6.12 we added this for (heavy) IMA use:
>
> tpm.disable_pcr_integrity= [HW,TPM]
> Do not protect PCR registers from unintended physical
> access, or interposers in the bus by the means of
> having an integrity protected session wrapped around
> TPM2_PCR_Extend command. Consider this in a situation
> where TPM is heavily utilized by IMA, thus protection
> causing a major performance hit, and the space where
> machines are deployed is by other means guarded.
>
> Similarly it might make sense to have "tpm.disable_random_integrity"
> that disables the feature introduced by the failing commit.
>
I am wondering what could be the not-so-obvious root cause for this?
Could it be due to a (TPM or RNG-related) lock? I guess the audio
popping could occur if an application cannot meet timing requirements
when it runs into some sort of blocking lock...
> What do you think?
> >>
>> Cheers,
>> Chris
>
> BR, Jarkko
>
next prev parent reply other threads:[~2024-12-02 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 0:11 Christian Heusel
2024-10-25 14:47 ` Jarkko Sakkinen
2024-11-26 11:42 ` Christian Heusel
2024-11-30 2:44 ` Jarkko Sakkinen
2024-12-02 22:15 ` Stefan Berger [this message]
2024-12-03 6:38 ` Jarkko Sakkinen
2024-12-09 12:58 ` 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=ce7fa562-7cb7-4adc-934a-560b94ce44f0@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=christian@heusel.eu \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=regressions@lists.linux.dev \
/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
all inboxes | Powered by JetHome®