[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090127225458.GA8756@linux-sh.org>
Date: Wed, 28 Jan 2009 07:54:59 +0900
From: Paul Mundt <lethal@...ux-sh.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: adrian@...golddream.dyndns.info, lkmladrian@...il.com,
linux-kernel@...r.kernel.org, linux-sh@...r.kernel.org,
penberg@...helsinki.fi, dbaryshkov@...il.com,
penguin-kernel@...ove.sakura.ne.jp, lg@...x.de, hannes@...xchg.org
Subject: Re: [PATCH] dma: fix up broken comparison in dma_alloc_from_coherent
On Tue, Jan 27, 2009 at 01:48:31PM -0800, Andrew Morton wrote:
> On Wed, 21 Jan 2009 17:11:19 +0900
> Paul Mundt <lethal@...ux-sh.org> wrote:
>
> > @@ -118,31 +118,32 @@ int dma_alloc_from_coherent(struct device *dev, ssize_t size,
> > mem = dev->dma_mem;
> > if (!mem)
> > return 0;
> > - if (unlikely(size > mem->size))
> > - return 0;
> > +
> > + *ret = NULL;
> > +
> > + if (unlikely(size > (mem->size << PAGE_SHIFT)))
> > + goto err;
>
> Looks a bit broken on 64-bit.
>
> `size' is ssize_t (long).
>
> `mem->size' is `int'.
>
> The left shift can overflow and cause badnesses.
>
> > + *dma_handle = mem->device_base + (pageno << PAGE_SHIFT);
> > + *ret = mem->virt_base + (pageno << PAGE_SHIFT);
>
> Ditto.
>
>
> Maybe it's a can't-happen (why?), but...
It is probably worth adding casts to avoid the potential for overflow,
but it's not likely that this would ever be a problem in practice.
Someone would need a pretty big per-device memory area for this to ever
overflow anyways, and if the device has that much memory, people are
probably going to want to do something else with it besides designating
all of it for DMA buffer usage ;-)
--
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