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: <20090206182052.GI27684@sequoia.sous-sol.org>
Date:	Fri, 6 Feb 2009 10:20:52 -0800
From:	Chris Wright <chrisw@...s-sol.org>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	Chris Wright <chrisw@...s-sol.org>,
	Joerg Roedel <joerg.roedel@....com>,
	fujita.tomonori@....ntt.co.jp, netdev@...r.kernel.org,
	iommu@...ts.linux-foundation.org, mingo@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/16] DMA-API debugging facility v2

* David Woodhouse (dwmw2@...radead.org) wrote:
> An alternative explanation... The DMA is aborted¹, and the device
> interrupts us to tell us about it at the _same_ time that the IOMMU
> interrupts us to tell us about the fault. We process the device
> interrupt first, unmap that buffer. And then we process the IOMMU
> interrupt... and the buffer is already gone from the list.

[  362.283661] Device 0000:03:00.0 mapping: 1000@...1b000
[  362.283727] DMAR:[DMA Write] Request device [03:00.0] fault addr fff1b000 
[  362.284719] Device 0000:03:00.0 unmapping: 1000@...1b000

[  362.426974] Device 0000:03:00.0 mapping: 1000@...1b000
[  362.427040] DMAR:[DMA Write] Request device [03:00.0] fault addr fff1b000 
[  362.429092] Device 0000:03:00.0 unmapping: 1000@...1b000

[  447.644332] Device 0000:03:00.0 mapping: 1000@...03000
[  447.644373] DMAR:[DMA Write] Request device [03:00.0] fault addr fff03000 
[  447.646008] Device 0000:03:00.0 unmapping: 1000@...03000

[  483.037641] Device 0000:03:00.0 mapping: 1000@...9f000
[  483.037707] DMAR:[DMA Write] Request device [03:00.0] fault addr ffc9f000 
[  483.038699] Device 0000:03:00.0 unmapping: 1000@...9f000

...

Looks like driver is doing the right thing.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ