linux-kernel - Re: [PATCH] iommu/amd: Mark interrupt as managed

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZcZLKtFrbLax9lYP@8bytes.org>
Date: Fri, 9 Feb 2024 16:56:26 +0100
From: Joerg Roedel <joro@...tes.org>
To: Mario Limonciello <mario.limonciello@....com>
Cc: suravee.suthikulpanit@....com, Vasant.Hegde@....com, will@...nel.org,
	robin.murphy@....com, iommu@...ts.linux.dev,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] iommu/amd: Mark interrupt as managed

On Fri, Feb 09, 2024 at 09:48:57AM -0600, Mario Limonciello wrote:
> Thanks!  This problem should go all the way to when MSI support was
> introduced (2.6.28):
> 
> a80dc3e0e0dc ("AMD IOMMU: add MSI interrupt support")

That makes most sense to me, also if it only uncovers with ...

> 
> But I don't think that's a correct fixes tag because
> irq_managed wasn't introduced until 3.19:
> 
> cffe0a2b5a34 ("x86, irq: Keep balance of IOAPIC pin reference count")

This one.

> But then I tried to go off the original introduction of the error message,
> but that's quite ancient.
> 
> 1da177e4c3f4 ("Linux-2.6.12-rc2")

That is not relevant, as the first AMD IOMMU driver was only merged for
2.6.27 :)

> Cc: stable@...r.kernel.org # 3.19+

That makes sense too.

Regards,

	Joerg