linux-kernel - Re: USB transfer_buffer allocations on 64bit systems

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 14 Apr 2010 11:38:26 -0700
From:	Chris Wright <chrisw@...s-sol.org>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	Daniel Mack <daniel@...aq.de>,
	David Woodhouse <dwmw2@...radead.org>,
	Greg KH <gregkh@...e.de>, USB list <linux-usb@...r.kernel.org>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	iommu@...ts.linux-foundation.org, Andi Kleen <andi@...stfloor.org>,
	Pedro Ribeiro <pedrib@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: USB transfer_buffer allocations on 64bit systems

* Alan Stern (stern@...land.harvard.edu) wrote:
> Since using mem=4096M or GFP_DMA stopped the symptoms, it seems very 
> likely that a buffer is getting allocated above the 4 GB line and not 
> bounced or IOMMU-mapped correctly.
> 
> David, do you have anything to suggest?  Any ways to check for IOMMU or 
> related errors?

Well if the IOMMU is enabled, dmesg will show you if you're getting DMA
faults due to IOMMU.  Doesn't sound like that's the case.

> The problem, in short, is that USB audio doesn't work properly when
> Pedro boots a 64-bit kernel on his 4-GB machine.  With a 32-bit kernel
> it works okay, and it also works if we use dma_alloc_coherent().  The
> host controller is limited to 32-bit DMA, and the DMA addresses
> generated by dma_map_single() appear to be normal.

So dma_map_single is the case that's failing, but you think the mask is
correct?  What about the direction?

> At the moment we don't even know if this is caused by a bug in the 
> kernel or a bug in Pedro's hardware.  But he has observed the same 
> problem on two different machines, both using the ICH9 chipset.

Is the IOMMU enabled?

$ dmesg | grep -e DMAR -e IOMMU

If it's on, you can boot w/out (intel_iommu=off) or in passthrough mode
(intel_iommu=on iommu=pt) and see if that makes a difference.

If it's not on (but there) you can enable it (intel_iommu=on) and look
for DMA faults (pointing to driver bug).

thanks,
-chris
--
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/