Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: ming.qian@oss.nxp.com
Cc: mchehab@kernel.org, hverkuil-cisco@xs4all.nl,
	mirela.rabulea@oss.nxp.com, shawnguo@kernel.org,
	s.hauer@pengutronix.de, kernel@pengutronix.de,
	festevam@gmail.com, xiahong.bao@nxp.com, eagle.zhou@nxp.com,
	linux-imx@nxp.com, imx@lists.linux.dev,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/4] media: imx-jpeg: Cleanup after an allocation error
Date: Wed, 9 Apr 2025 17:55:08 -0400	[thread overview]
Message-ID: <Z/bsvC5txo3aL9QF@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20250408025725.1244-3-ming.qian@oss.nxp.com>

On Tue, Apr 08, 2025 at 10:57:18AM +0800, ming.qian@oss.nxp.com wrote:
> From: Ming Qian <ming.qian@oss.nxp.com>
>
> When allocation failures are not cleaned up by the driver, further
> allocation errors will be false-positives, which will cause buffers to
> remain uninitialized and cause NULL pointer dereferences.
...
> Clean up the errors accordingly.

Ensure proper cleanup of failed allocations to prevent these issues.

>
> Fixes: 2db16c6ed72c ("media: imx-jpeg: Add V4L2 driver for i.MX8 JPEG Encoder/Decoder")
> Signed-off-by: Ming Qian <ming.qian@oss.nxp.com>
> Reviewed-by: Frank Li <Frank.Li@nxp.com>
> ---
> v3
> - Split the moving of code into a separate patch
>
> v2
> - Add the Fixes tag
>
>  drivers/media/platform/nxp/imx-jpeg/mxc-jpeg.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/media/platform/nxp/imx-jpeg/mxc-jpeg.c b/drivers/media/platform/nxp/imx-jpeg/mxc-jpeg.c
> index b2f7e9ad1885..12661c177f5a 100644
> --- a/drivers/media/platform/nxp/imx-jpeg/mxc-jpeg.c
> +++ b/drivers/media/platform/nxp/imx-jpeg/mxc-jpeg.c
> @@ -820,6 +820,7 @@ static bool mxc_jpeg_alloc_slot_data(struct mxc_jpeg_dev *jpeg)
>  	return true;
>  err:
>  	dev_err(jpeg->dev, "Could not allocate descriptors for slot %d", jpeg->slot_data.slot);
> +	mxc_jpeg_free_slot_data(jpeg);
>
>  	return false;
>  }
> --
> 2.43.0-rc1
>


  reply	other threads:[~2025-04-09 22:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08  2:57 [PATCH v3 0/4] media: imx-jpeg: Fix some motion-jpeg decoding issues ming.qian
2025-04-08  2:57 ` [PATCH v3 1/4] media: imx-jpeg: Move mxc_jpeg_free_slot_data() ahead ming.qian
2025-04-09 20:22   ` Nicolas Dufresne
2025-04-09 21:50   ` Frank Li
2025-04-08  2:57 ` [PATCH v3 2/4] media: imx-jpeg: Cleanup after an allocation error ming.qian
2025-04-09 21:55   ` Frank Li [this message]
2025-04-08  2:57 ` [PATCH v3 3/4] media: imx-jpeg: Change the pattern size to 128x64 ming.qian
2025-04-09 22:04   ` Frank Li
2025-04-08  2:57 ` [PATCH v3 4/4] media: imx-jpeg: Check decoding is ongoing for motion-jpeg ming.qian
2025-04-09 22:18   ` Frank Li

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=Z/bsvC5txo3aL9QF@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=eagle.zhou@nxp.com \
    --cc=festevam@gmail.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=ming.qian@oss.nxp.com \
    --cc=mirela.rabulea@oss.nxp.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=xiahong.bao@nxp.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