From: "Ming Qian(OSS)" <ming.qian@oss.nxp.com>
To: Sebastian Fricke <sebastian.fricke@collabora.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 v2 1/3] media: imx-jpeg: Enhance error handling in buffer allocation
Date: Mon, 7 Apr 2025 10:52:10 +0800 [thread overview]
Message-ID: <92c8f778-cd94-4113-8b9e-699b8ffa9fa2@oss.nxp.com> (raw)
In-Reply-To: <20250405113936.oepkmoz2czytbuxy@basti-XPS-13-9310>
Hi Sebastian,
On 2025/4/5 19:39, Sebastian Fricke wrote:
> Hey Ming,
>
> In the title I'd suggest:
> media: imx-jpeg: Cleanup after an allocation error
>
> To be a bit more concrete, enhance error handling can mean pretty much
> anything.
>
Thanks, I'll apply your suggestion
> On 28.03.2025 14:30, 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.
>
> I'd suggest:
>
> 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.
>
Thanks, I'll apply your suggestion
>>
>> Fixes: 2db16c6ed72c ("media: imx-jpeg: Add V4L2 driver for i.MX8 JPEG
>> Encoder/Decoder")
>> Signed-off-by: Ming Qian <ming.qian@oss.nxp.com>
>> ---
>> v2
>> - Add the Fixes tag
>>
>> .../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;
>> -}
>
> Can you split the moving of the code from the changes you do?
> Otherwise the reviewer is forced to get the diff manually.
Sure, this will be done in v3
>
> Regards,
> Sebastian Fricke
next prev parent reply other threads:[~2025-04-07 2:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 6:30 [PATCH v2 0/3] media: imx-jpeg: Fix some motion-jpeg decoding issues ming.qian
2025-03-28 6:30 ` [PATCH v2 1/3] media: imx-jpeg: Enhance error handling in buffer allocation ming.qian
2025-03-28 14:27 ` Frank Li
2025-04-05 11:39 ` Sebastian Fricke
2025-04-07 2:52 ` Ming Qian(OSS) [this message]
2025-03-28 6:30 ` [PATCH v2 2/3] media: imx-jpeg: Change the pattern size to 128x64 ming.qian
2025-03-28 14:28 ` Frank Li
2025-04-05 15:26 ` Sebastian Fricke
2025-04-07 2:54 ` Ming Qian(OSS)
2025-03-28 6:30 ` [PATCH v2 3/3] media: imx-jpeg: Check decoding is ongoing for motion-jpeg ming.qian
2025-03-28 14:45 ` Frank Li
2025-03-31 3:10 ` Ming Qian(OSS)
2025-03-31 14:32 ` Frank Li
2025-04-01 3:17 ` Ming Qian(OSS)
2025-04-01 14:37 ` Frank Li
2025-04-02 5:34 ` Ming Qian(OSS)
2025-04-02 18:03 ` Frank Li
2025-04-03 6:23 ` Ming Qian(OSS)
2025-04-05 15:37 ` Sebastian Fricke
2025-04-07 5:14 ` 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=92c8f778-cd94-4113-8b9e-699b8ffa9fa2@oss.nxp.com \
--to=ming.qian@oss.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=sebastian.fricke@collabora.com \
--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