From: Vinod Koul <vkoul@kernel.org>
To: Yu Liao <liaoyu15@huawei.com>
Cc: liwei391@huawei.com, dmaengine@vger.kernel.org
Subject: Re: [PATCH -next 1/2] dmaengine: fsl-edma: use struct_size() helper
Date: Mon, 21 Aug 2023 11:17:54 +0530 [thread overview]
Message-ID: <ZOL6ior65updLbea@matsya> (raw)
In-Reply-To: <20230816020355.3002617-1-liaoyu15@huawei.com>
On 16-08-23, 10:03, Yu Liao wrote:
> Make use of the struct_size() helper instead of an open-coded version,
> in order to avoid any potential type mistakes or integer overflows that,
> in the worst scenario, could lead to heap overflows.
>
> Signed-off-by: Yu Liao <liaoyu15@huawei.com>
> ---
> drivers/dma/fsl-edma.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/dma/fsl-edma.c b/drivers/dma/fsl-edma.c
> index e40769666e39..caca3566ba82 100644
> --- a/drivers/dma/fsl-edma.c
> +++ b/drivers/dma/fsl-edma.c
> @@ -270,7 +270,6 @@ static int fsl_edma_probe(struct platform_device *pdev)
> struct device_node *np = pdev->dev.of_node;
> struct fsl_edma_engine *fsl_edma;
> const struct fsl_edma_drvdata *drvdata = NULL;
> - struct fsl_edma_chan *fsl_chan;
> struct edma_regs *regs;
> int len, chans;
> int ret, i;
> @@ -288,7 +287,7 @@ static int fsl_edma_probe(struct platform_device *pdev)
> return ret;
> }
>
> - len = sizeof(*fsl_edma) + sizeof(*fsl_chan) * chans;
> + len = struct_size(fsl_edma, chans, chans);
> fsl_edma = devm_kzalloc(&pdev->dev, len, GFP_KERNEL);
Drop len and use struct_size() here...
> if (!fsl_edma)
> return -ENOMEM;
> --
> 2.25.1
--
~Vinod
next prev parent reply other threads:[~2023-08-21 5:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 2:03 [PATCH -next 1/2] dmaengine: fsl-edma: use struct_size() helper Yu Liao
2023-08-16 2:03 ` [PATCH -next 2/2] dmaengine: mcf-edma: " Yu Liao
2023-08-21 5:48 ` Vinod Koul
2023-08-21 5:47 ` Vinod Koul [this message]
2023-08-21 6:06 ` [PATCH -next 1/2] dmaengine: fsl-edma: " Yu Liao
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=ZOL6ior65updLbea@matsya \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=liaoyu15@huawei.com \
--cc=liwei391@huawei.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