linux-kernel - Re: uhci_hcd: DMA-API: cpu touching an active dma mapped cacheline

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] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.1403061443110.961-100000@iolanthe.rowland.org>
Date:	Thu, 6 Mar 2014 14:48:26 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Dan Williams <dan.j.williams@...el.com>
cc:	Dave Jones <davej@...hat.com>, Joerg Roedel <joerg.roedel@....com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	USB list <linux-usb@...r.kernel.org>
Subject: Re: uhci_hcd: DMA-API: cpu touching an active dma mapped cacheline

On Thu, 6 Mar 2014, Dan Williams wrote:

> >>> Mapped at:
> >>>  [<c13081b5>] debug_dma_alloc_coherent+0x2b/0xc3
> >>>  [<c116fcee>] dma_pool_alloc+0x14f/0x2fd
> >>>  [<c1456eaa>] uhci_alloc_td.isra.35+0x24/0x60
> >>>  [<c1457fa6>] uhci_start+0x272/0x56b
> >>>  [<c142d8fb>] usb_add_hcd+0x252/0x774
> >>
> >> I don't get it.  As the name indicates, debug_dma_alloc_coherent should
> >> give us consistent memory -- meaning that the CPU is allowed to access
> >> the memory while DMA is in progress, without worrying about caching
> >> effects (see Documentation/DMA-API.txt).
> >>
> >> So why should we get a warning when the CPU accesses this memory?  Is
> >> this a regression in the DMA debug library?
> >
> > Yes, it seems so.  alloc_coherent needs to be exempt from active
> > mapping tracking.  Fix coming up.
> >
> 
> Actually I'm not so sure.  Yes, alloc_coherent means the cpu can
> touch, but if that page is COW'd how can you be sure that the copy
> gets the most up to date data from the device?  This check is
> asserting that dma might be colliding with a copy-on-write event.

dma_pool_create should never return memory that requires COW.  How 
would the system know when to do the copies?

Alan Stern

--
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/