Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ming Qian(OSS)" <ming.qian@oss.nxp.com>
To: Frank Li <Frank.li@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 1/3] media: imx-jpeg: Enhance error handling in buffer allocation
Date: Fri, 28 Mar 2025 09:22:48 +0800	[thread overview]
Message-ID: <6aae465e-e41b-4144-a105-6424bfe1d11e@oss.nxp.com> (raw)
In-Reply-To: <Z+ViNIB7WqgmouYE@lizhi-Precision-Tower-5810>

Hi Frank,

On 2025/3/27 22:35, Frank Li wrote:
> On Thu, Mar 27, 2025 at 10:37:05AM +0800, ming.qian@oss.nxp.com wrote:
>> From: Ming Qian <ming.qian@oss.nxp.com>
>>
>> In function mxc_jpeg_alloc_slot_data, driver will allocate some dma
>> buffer, but only return error if certain allocation failed.
>>
>> Without cleanup the allocation failure, the next time it will return
>> success directly, but let some buffer be uninitialized.
>> It may result in accessing a null pointer.
>>
>> Clean up if error occurs in the allocation.
>>
>> Signed-off-by: Ming Qian <ming.qian@oss.nxp.com>
> 
> Look like it is bug fix, add fixes tags

Yes, I missed it, I will add it in v2

Thanks,
Ming

> 
> Frank
>> ---
>>   .../media/platform/nxp/imx-jpeg/mxc-jpeg.c    | 47 +++++++++++--------
>>   1 file changed, 27 insertions(+), 20 deletions(-)
>>
>> diff --git a/drivers/media/platform/nxp/imx-jpeg/mxc-jpeg.c b/drivers/media/platform/nxp/imx-jpeg/mxc-jpeg.c
>> index 0e6ee997284b..12661c177f5a 100644
>> --- a/drivers/media/platform/nxp/imx-jpeg/mxc-jpeg.c
>> +++ b/drivers/media/platform/nxp/imx-jpeg/mxc-jpeg.c
>> @@ -752,6 +752,32 @@ static int mxc_get_free_slot(struct mxc_jpeg_slot_data *slot_data)
>>   	return -1;
>>   }
>>
>> +static void mxc_jpeg_free_slot_data(struct mxc_jpeg_dev *jpeg)
>> +{
>> +	/* free descriptor for decoding/encoding phase */
>> +	dma_free_coherent(jpeg->dev, sizeof(struct mxc_jpeg_desc),
>> +			  jpeg->slot_data.desc,
>> +			  jpeg->slot_data.desc_handle);
>> +	jpeg->slot_data.desc = NULL;
>> +	jpeg->slot_data.desc_handle = 0;
>> +
>> +	/* free descriptor for encoder configuration phase / decoder DHT */
>> +	dma_free_coherent(jpeg->dev, sizeof(struct mxc_jpeg_desc),
>> +			  jpeg->slot_data.cfg_desc,
>> +			  jpeg->slot_data.cfg_desc_handle);
>> +	jpeg->slot_data.cfg_desc_handle = 0;
>> +	jpeg->slot_data.cfg_desc = NULL;
>> +
>> +	/* free configuration stream */
>> +	dma_free_coherent(jpeg->dev, MXC_JPEG_MAX_CFG_STREAM,
>> +			  jpeg->slot_data.cfg_stream_vaddr,
>> +			  jpeg->slot_data.cfg_stream_handle);
>> +	jpeg->slot_data.cfg_stream_vaddr = NULL;
>> +	jpeg->slot_data.cfg_stream_handle = 0;
>> +
>> +	jpeg->slot_data.used = false;
>> +}
>> +
>>   static bool mxc_jpeg_alloc_slot_data(struct mxc_jpeg_dev *jpeg)
>>   {
>>   	struct mxc_jpeg_desc *desc;
>> @@ -794,30 +820,11 @@ 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;
>>   }
>>
>> -static void mxc_jpeg_free_slot_data(struct mxc_jpeg_dev *jpeg)
>> -{
>> -	/* free descriptor for decoding/encoding phase */
>> -	dma_free_coherent(jpeg->dev, sizeof(struct mxc_jpeg_desc),
>> -			  jpeg->slot_data.desc,
>> -			  jpeg->slot_data.desc_handle);
>> -
>> -	/* free descriptor for encoder configuration phase / decoder DHT */
>> -	dma_free_coherent(jpeg->dev, sizeof(struct mxc_jpeg_desc),
>> -			  jpeg->slot_data.cfg_desc,
>> -			  jpeg->slot_data.cfg_desc_handle);
>> -
>> -	/* free configuration stream */
>> -	dma_free_coherent(jpeg->dev, MXC_JPEG_MAX_CFG_STREAM,
>> -			  jpeg->slot_data.cfg_stream_vaddr,
>> -			  jpeg->slot_data.cfg_stream_handle);
>> -
>> -	jpeg->slot_data.used = false;
>> -}
>> -
>>   static void mxc_jpeg_check_and_set_last_buffer(struct mxc_jpeg_ctx *ctx,
>>   					       struct vb2_v4l2_buffer *src_buf,
>>   					       struct vb2_v4l2_buffer *dst_buf)
>> --
>> 2.43.0-rc1
>>


  reply	other threads:[~2025-03-28  1:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-27  2:37 [PATCH 0/3] media: imx-jpeg: Fix some motion-jpeg decoding issues ming.qian
2025-03-27  2:37 ` [PATCH 1/3] media: imx-jpeg: Enhance error handling in buffer allocation ming.qian
2025-03-27 14:35   ` Frank Li
2025-03-28  1:22     ` Ming Qian(OSS) [this message]
2025-03-27  2:37 ` [PATCH 2/3] media: imx-jpeg: Change the pattern size to 128x64 ming.qian
2025-03-27  2:37 ` [PATCH 3/3] media: imx-jpeg: Check decoding is ongoing for motion-jpeg ming.qian
2025-03-27 14:41   ` Frank Li
2025-03-28  1:30     ` Ming Qian(OSS)

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=6aae465e-e41b-4144-a105-6424bfe1d11e@oss.nxp.com \
    --to=ming.qian@oss.nxp.com \
    --cc=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=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