From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wentao Liang <vulab@iscas.ac.cn>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Peter Griffin <peter.griffin@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>
Cc: linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] media: exynos4-is: Free control handler if fimc-lite subdev init fails
Date: Wed, 4 Nov 2026 08:21:14 +0100 [thread overview]
Message-ID: <794a43d2-74be-46ce-a779-f7227a82516e@kernel.org> (raw)
In-Reply-To: <20261103094617.1289377-1-vulab@iscas.ac.cn>
On 03/11/2026 10:46, Wentao Liang wrote:
> fimc_lite_create_capture_subdev() initializes fimc->ctrl_handler and adds
> a control to it. If the control cannot be created, handler->error is set
> and the function returns after cleaning up the media entity only. The
> control handler still owns the memory allocated for its buckets and for
> any control created before the failure, and fimc_lite_probe() does not
> call fimc_lite_unregister_capture_subdev() on this error, so that memory
> is leaked.
>
> Free the control handler before returning the error.
>
> Fixes: 4af813108b88 ("[media] s5p-fimc: Add support for Exynos4x12 FIMC-LITE")
> Cc: stable@vger.kernel.org
> Assisted-by: DeepSeek-V4.1-Flash and OpenAI Codex
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
This is another posting of bot ignoring feedback and probably
introducing vilnerabilities hidden in big spam posting.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-11-04 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 9:46 Wentao Liang
2026-11-03 10:26 ` Krzysztof Kozlowski
2026-11-04 7:21 ` Krzysztof Kozlowski [this message]
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=794a43d2-74be-46ce-a779-f7227a82516e@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=peter.griffin@linaro.org \
--cc=s.nawrocki@samsung.com \
--cc=stable@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
/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
all inboxes | Powered by JetHome®