[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20100804231727H.fujita.tomonori@lab.ntt.co.jp>
Date: Wed, 4 Aug 2010 23:18:16 +0900
From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To: Joerg.Roedel@....com
Cc: fujita.tomonori@....ntt.co.jp, subrata@...ux.vnet.ibm.com,
linux-kernel@...r.kernel.org, Linuxppc-dev@...abs.org,
grant.likely@...retlab.ca, James.Bottomley@...e.de,
brking@...ux.vnet.ibm.com, tj@...nel.org, rcj@...ux.vnet.ibm.com,
devilbis@...ibm.com, santil@...ibm.com, sleddog@...ibm.com,
sachinp@...ux.vnet.ibm.com, dipraksh@...ux.vnet.ibm.com
Subject: Re: 2.6.35-stable/ppc64/p7: Badness at lib/dma-debug.c:902, Call
Trace & Instruction Dump during boot
On Wed, 4 Aug 2010 15:16:34 +0200
"Roedel, Joerg" <Joerg.Roedel@....com> wrote:
> On Mon, Aug 02, 2010 at 07:55:03AM -0400, FUJITA Tomonori wrote:
> > I guess that this driver does a partial sync with
> > dma_sync_single_for_* API. dma-debug can't handle it properly. It's
> > likely that this is a false warning.
>
> If this turns out to be true it is not trivial to fix. I prepare a patch
> to test for you.
I've not looked at the details of this driver, but there are drivers
that do such. So dma-debug needs to be fixed anyway; you can't assume
that a DMA address that dma_map_single returned is passed to
dma_sync_single_for API.
--
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