linux-kernel - Re: dw_dmac driver questions

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]

Date:	Tue, 06 Jan 2009 10:33:44 +0900 (JST)
From:	Atsushi Nemoto <anemo@....ocn.ne.jp>
To:	haavard.skinnemoen@...el.com
Cc:	anemo@....ocn.ne.jp, linux-kernel@...r.kernel.org,
	maciej.sosnowski@...el.com, dan.j.williams@...el.com
Subject: Re: dw_dmac driver questions

On Mon, 5 Jan 2009 16:48:47 +0100, Haavard Skinnemoen <haavard.skinnemoen@...el.com> wrote:
> > Well, I'm confused...  I reference atmel-mci for client and dw_dmac
> > for dma engine.  Currently, dw_dmac calls dma_map_sg() and atmel-mci
> > calls dma_unmap_sg().  Do you mean atmel-mci will be changed to call
> > dma_map_sg()?
> 
> Yes, I think it should.
> 
> Preferably, I'd like the client to do both mapping and unmapping in all
> cases since it knows best what's actually needed. For example, some
> drivers may be using DMA-coherent buffers, which don't need to be
> mapped at all.

I see, thanks.

> > > > 4. This is a comment on head of dwc_handle_error().
> > > > 
> > > > 	/*
> > > > 	 * The descriptor currently at the head of the active list is
> > > > 	 * borked. Since we don't have any way to report errors, we'll
> > > > 	 * just have to scream loudly and try to carry on.
> > > > 	 */
> > > > 
> > > > But, the bad descriptor can be at any place of the active list, no ?
> > > > For example, if the active list contained two descriptor and latter
> > > > was broken and tasklet was delayed by some reason, the head of the
> > > > list should be good.  
> > > 
> > > Since dwc_scan_descriptors() was just called, all descriptors that were
> > > completed successfully have been removed from the active list. So the
> > > first entry must be the broken one.  
> > 
> > But the removal from the active list is done in tasklet too.  If the
> > CPU was slow and DMA engine was fast enough, DMA engine will process
> > multiple descriptors before the tasklet called, no ?
> 
> The DMA engine stops if it encounters a bad address.

Yes.  And it does not mean the bad descriptor is at head of the active
queue.

1) driver enqueue desc A to active list and start DMA engine
2) driver enqueue desc B to queue list
3) driver enqueue desc C to queue list  (desc C contains bad address)
4) DMA engine finish desc A and raise interrupt
5) tasklet remove desc A from active list and move desc B and C to active list
6) DMA engine finish desc B and raise interrupt
7) DMA engine abort desc C and raise interrupt
8) tasklet detect error

The point is the order of (7) and (8) cannot be expected.  If (7)
comes first, the head of the active list contains desc B at (8) and
that is not a bad descriptor.

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