From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shuah Khan Subject: Re: [PATCH 3.4] iommu/amd: Initialize device table after dma_ops Date: Thu, 28 Feb 2013 14:22:55 -0700 Message-ID: <1362086575.2822.38.camel@lorien2> References: <1360205128.2615.14.camel@lorien2> <1361922545.2720.17.camel@lorien2> <1362081120.2822.30.camel@lorien2> Reply-To: shuah.khan@hp.com Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1362081120.2822.30.camel@lorien2> Sender: stable-owner@vger.kernel.org To: Joerg Roedel , luis.henriques@canonical.com Cc: iommu@lists.linux-foundation.org, stable , Greg KH , shuahkhan@gmail.com List-Id: iommu@lists.linux-foundation.org On Thu, 2013-02-28 at 12:52 -0700, Shuah Khan wrote: > On Tue, 2013-02-26 at 16:49 -0700, Shuah Khan wrote: > > When dma_ops are initialized the unity mappings are created. The > > init_device_table_dma() function makes sure DMA from all devices is > > blocked by default. This opens a short window in time where DMA to > > unity mapped regions is blocked by the IOMMU. Make sure this does not > > happen by initializing the device table after dma_ops. > > > > Back-port upstream commit: f528d980c17b8714aedc918ba86e058af914d66b > > > > Signed-off-by: Joerg Roedel > > Signed-off-by: Shuah Khan > > CC: stable@vger.kernel.org 3.4 > > Please consider this for 3.5 as well. > > -- Shuah Please consider this for 3.5. Patch applies and fix works on 3.5.7. My previous reply to Herton Ronaldo Krzesinski bounced. Including Luis Henriques on this one. -- Shuah