From: Robin Murphy <robin.murphy@arm.com>
To: Kevin Grandemange <kevin.grandemange@allegrodvt.com>,
Christoph Hellwig <hch@lst.de>
Cc: "iommu@lists.linux-foundation.org" <iommu@lists.linux-foundation.org>
Subject: Re: [PATCH] [dma-coherent] Fix integer overflow in the reserved-memory dma allocation
Date: Mon, 9 Mar 2020 13:56:50 +0000 [thread overview]
Message-ID: <6b2b656c-33ee-4e02-e687-c71ff43de584@arm.com> (raw)
In-Reply-To: <20200309110134.7672-1-kevin.grandemange@allegrodvt.com>
On 09/03/2020 11:02 am, Kevin Grandemange wrote:
> pageno is an int and the PAGE_SHIFT shift is done on an int,
> overflowing if the memory is bigger than 2G
>
> This can be reproduced using for example a reserved-memory of 4G
Nit: the example shows 16GB, not 4.
> reserved-memory {
> #address-cells = <2>;
> #size-cells = <2>;
> ranges;
>
> reserved_dma: buffer@0 {
> compatible = "shared-dma-pool";
> no-map;
> reg = <0x5 0x00000000 0x4 0x0>;
> };
> };
>
> Signed-off-by: Kevin Grandemange <kevin.grandemange@allegrodvt.com>
> ---
> kernel/dma/coherent.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/dma/coherent.c b/kernel/dma/coherent.c
> index 551b0eb7028a..c20c6c0635b7 100644
> --- a/kernel/dma/coherent.c
> +++ b/kernel/dma/coherent.c
> @@ -130,6 +130,7 @@ static void *__dma_alloc_from_coherent(struct device *dev,
> int order = get_order(size);
> unsigned long flags;
> int pageno;
> + ssize_t mem_offset;
> void *ret;
>
> spin_lock_irqsave(&mem->spinlock, flags);
> @@ -144,8 +145,9 @@ static void *__dma_alloc_from_coherent(struct device *dev,
> /*
> * Memory was found in the coherent area.
> */
> - *dma_handle = dma_get_device_base(dev, mem) + (pageno << PAGE_SHIFT);
> - ret = mem->virt_base + (pageno << PAGE_SHIFT);
> + mem_offset = (ssize_t)pageno << PAGE_SHIFT;
Isn't this still capable of overflowing for 32-bit architectures where
ssize_t is most likely to be long and LONG_MAX == INT_MAX (before we
even get to PAE and friends)? Logically, dma_addr_t would be the most
appropriate type here.
FWIW since you have to have an explicit cast either way, I don't see
much point in introducing the local variable vs. just adding the cast
into the existing expression.
Thanks,
Robin.
> + *dma_handle = dma_get_device_base(dev, mem) + mem_offset;
> + ret = mem->virt_base + mem_offset;
> spin_unlock_irqrestore(&mem->spinlock, flags);
> memset(ret, 0, size);
> return ret;
>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-03-09 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 11:02 [PATCH] [dma-coherent] Fix integer overflow in the reserved-memory dma allocation Kevin Grandemange
2020-03-09 13:56 ` Robin Murphy [this message]
2020-03-09 14:45 ` Kevin Grandemange
2020-03-09 15:22 ` [PATCH v2] " Kevin Grandemange
2020-03-12 15:41 ` [PATCH v3] " Kevin Grandemange
2020-03-16 9:43 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6b2b656c-33ee-4e02-e687-c71ff43de584@arm.com \
--to=robin.murphy@arm.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=kevin.grandemange@allegrodvt.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.