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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <CY54PJM8KY92.UOCXW1JQUVF7@suppilovahvero>
Date: Wed, 03 Jan 2024 16:08:39 +0200
From: "Jarkko Sakkinen" <jarkko@...nel.org>
To: João Paulo Silva Gonçalves
 <joao.goncalves@...adex.com>, "linux-kernel@...r.kernel.org"
 <linux-kernel@...r.kernel.org>, "peterhuewe@....de" <peterhuewe@....de>,
 "jgg@...pe.ca" <jgg@...pe.ca>, "linux-integrity@...r.kernel.org"
 <linux-integrity@...r.kernel.org>
Cc: "l.sanfilippo@...bus.com" <l.sanfilippo@...bus.com>,
 "Alexander.Steffen@...ineon.com" <Alexander.Steffen@...ineon.com>
Subject: Re: TPM interrupt patch on LTS

On Tue Dec 26, 2023 at 4:50 PM EET, João Paulo Silva Gonçalves wrote:
> Hello, 
>
> We are integrating a SPI TPM from Infineon with 6.1/5.15 LTS kernels for an 
> embedded platform and it is giving an error message that interrupts are not working. 
> There is a correction from [1] already on upstream but the patch that makes 
> interrupts work, commit e644b2f498d2 ("tpm, tpm_tis: Enable interrupt test"), was 
> not backported to LTS. This seems to be the only patch that was no backported 
> from [1]. I read some discussion on lkml about TPM interrupts problems but did 
> not get if it is related or the reason for not backporting the patch. 
>
> Do you know the reason this single patch was not backported?  
>
> [1] https://lore.kernel.org/lkml/20221124135538.31020-1-LinoSanfilippo@gmx.de/
>
> Thanks!
>
> Regards,
> Joao Paulo Goncalves

You can disable interrupts with "interrupts" kernel command-line
parameter. It's not backported because essentialy it is a feature,
i.e. interrupts have been never working before properly.

BR, Jarkko

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ