linux-kernel - Re: [ 117/175] iommu/amd: Make sure IOMMU interrupts are re-enabled on resume

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]

Date:	Tue, 03 Apr 2012 04:28:06 +0100
From:	Ben Hutchings <ben@...adent.org.uk>
To:	Greg KH <gregkh@...uxfoundation.org>,
	Joerg Roedel <joerg.roedel@....com>
Cc:	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	alan@...rguk.ukuu.org.uk
Subject: Re: [ 117/175] iommu/amd: Make sure IOMMU interrupts are re-enabled
 on resume

On Fri, 2012-03-30 at 12:50 -0700, Greg KH wrote:
> 3.3-stable review patch.  If anyone has any objections, please let me know.
> 
> ------------------
> 
> From: Joerg Roedel <joerg.roedel@....com>
> 
> commit 9ddd592a191b32f2ee6c4b6ed2bd52665c3a49f5 upstream.
> 
> Unfortunatly the interrupts for the event log and the
> peripheral page-faults are only enabled at boot but not
> re-enabled at resume. Fix that.
[...]

It looks like this should be applicable to 3.0 and 3.2 as well, but only
for the event log.  I'm attaching my (untested) backports for
consideration.

Ben.

-- 
Ben Hutchings
Reality is just a crutch for people who can't handle science fiction.

Content of type "text/x-patch" skipped

Content of type "text/x-patch" skipped

Download attachment "signature.asc" of type "application/pgp-signature" (829 bytes)