On Mon, Feb 9, 2015 at 8:19 PM, Tomasz Figa <tfiga at chromium.org> wrote: > Even though the code uses the dt_lock spin lock to serialize mapping > operation from different threads, it does not protect from IOMMU > accesses that might be already taking place and thus altering state > of the IOTLB. This means that current mapping code which first zaps > the page table and only then updates it with new mapping which is > prone to mentioned race. Oops, forgot to remove the "CHROMIUM" tag. Is that something that could be fixed when applying (if the patch is otherwise okay) or should I resend? Best regards, Tomasz
