linux-kernel - Re: [PATCH 3.2] iommu/amd: Initialize device table after dma

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: <1363491758.3937.239.camel@deadeye.wl.decadent.org.uk>
Date:	Sun, 17 Mar 2013 03:42:38 +0000
From:	Ben Hutchings <ben@...adent.org.uk>
To:	Joerg Roedel <joro@...tes.org>
Cc:	shuah.khan@...com, iommu@...ts.linux-foundation.org,
	LKML <linux-kernel@...r.kernel.org>,
	stable <stable@...r.kernel.org>,
	Greg KH <gregkh@...uxfoundation.org>, shuahkhan@...il.com
Subject: Re: [PATCH 3.2] iommu/amd: Initialize device table after dma_ops

On Sun, 2013-03-03 at 23:58 +0100, Joerg Roedel wrote:
> Hi Ben,
> 
> On Sat, Mar 02, 2013 at 11:00:35PM +0000, Ben Hutchings wrote:
> > I'm not convinced about this backport, because the order of
> > initialisation already changed a lot after 3.2 and before the upstream
> > commit.  So I'm going to wait for Joerg to confirm that this makes sense
> > before adding it to the patch queue.
> 
> The patch looks good, it fixes a race condition during amd_iommu
> initialization. I'll also gave the backport a test to be sure it
> doesn't break anything.

Applied, thanks all.

Ben.

-- 
Ben Hutchings
Usenet is essentially a HUGE group of people passing notes in class.
                      - Rachel Kadel, `A Quick Guide to Newsgroup Etiquette'

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