From: Robin Murphy <robin.murphy@arm.com>
To: Barry Song <song.bao.hua@hisilicon.com>,
hch@lst.de, m.szyprowski@samsung.com
Cc: iommu@lists.linux-foundation.org, linuxarm@huawei.com,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] dma-mapping: benchmark: check the validity of dma mask bits
Date: Fri, 18 Dec 2020 18:09:58 +0000 [thread overview]
Message-ID: <69d8ff1a-8993-758f-1aec-e133024cf0b7@arm.com> (raw)
In-Reply-To: <20201212101844.23612-1-song.bao.hua@hisilicon.com>
On 2020-12-12 10:18, Barry Song wrote:
> While dma_mask_bits is larger than 64, the bahvaiour is undefined. On the
> other hand, dma_mask_bits which is smaller than 20 (1MB) makes no sense
> in real hardware.
>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Barry Song <song.bao.hua@hisilicon.com>
> ---
> kernel/dma/map_benchmark.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/kernel/dma/map_benchmark.c b/kernel/dma/map_benchmark.c
> index b1496e744c68..19f661692073 100644
> --- a/kernel/dma/map_benchmark.c
> +++ b/kernel/dma/map_benchmark.c
> @@ -214,6 +214,12 @@ static long map_benchmark_ioctl(struct file *file, unsigned int cmd,
> return -EINVAL;
> }
>
> + if (map->bparam.dma_bits < 20 ||
FWIW I don't think we need to bother with a lower limit here - it's
unsigned, and a pointlessly small value will fail gracefully when we
come to actually set the mask anyway. We only need to protect kernel
code from going wrong, not userspace from being stupid to its own detriment.
Robin.
> + map->bparam.dma_bits > 64) {
> + pr_err("invalid dma_bits\n");
> + return -EINVAL;
> + }
> +
> if (map->bparam.node != NUMA_NO_NODE &&
> !node_possible(map->bparam.node)) {
> pr_err("invalid numa node\n");
>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-12-18 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 10:18 [PATCH] dma-mapping: benchmark: check the validity of dma mask bits Barry Song
2020-12-18 18:09 ` Robin Murphy [this message]
2020-12-19 3:15 ` Song Bao Hua (Barry Song)
2020-12-21 13:25 ` Robin Murphy
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=69d8ff1a-8993-758f-1aec-e133024cf0b7@arm.com \
--to=robin.murphy@arm.com \
--cc=dan.carpenter@oracle.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linuxarm@huawei.com \
--cc=m.szyprowski@samsung.com \
--cc=song.bao.hua@hisilicon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).