[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110324082521.GB9844@n2100.arm.linux.org.uk>
Date: Thu, 24 Mar 2011 08:25:21 +0000
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Nicolas Ferre <nicolas.ferre@...el.com>
Cc: dedekind1@...il.com,
"'linux-arm-kernel@...ts.infradead.org'"
<linux-arm-kernel@...ts.infradead.org>,
Linux Kernel list <linux-kernel@...r.kernel.org>,
Patrice VILCHEZ <patrice.vilchez@...el.com>,
Hong XU <hong.xu@...el.com>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>,
Andrew Victor <linux@...im.org.za>,
linux-mtd <linux-mtd@...ts.infradead.org>
Subject: Re: Hit BUG_ON in dma-mapping.c:425 (RFC)
On Thu, Mar 24, 2011 at 04:18:13PM +0800, Nicolas Ferre wrote:
> diff --git a/drivers/spi/atmel_spi.c b/drivers/spi/atmel_spi.c
> --- a/drivers/spi/atmel_spi.c
> +++ b/drivers/spi/atmel_spi.c
> @@ -647,6 +647,22 @@ static void atmel_spi_next_message(struct spi_master *master)
> atmel_spi_next_xfer(master, msg);
> }
>
> +static void *adjust_buffer_location(struct device *dev, void *buf)
> +{
> + if (likely(buf < high_memory)) {
> + return buf;
> + } else {
> + struct page *pg;
> +
> + pg = vmalloc_to_page(buf);
> + if (pg == 0) {
> + dev_err(dev, "failed to vmalloc_to_page\n");
> + return NULL;
> + }
> + return page_address(pg) + ((size_t)buf & ~PAGE_MASK);
> + }
> +}
> +
This really doesn't fix the problem. If the page is read or written via
the vmalloc mapping, you'll have stale data.
DMA to vmalloc areas is dodgy at best.
--
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