From: Markus Elfring <Markus.Elfring@web.de>
To: Zhang Shurong <zhang_shurong@foxmail.com>, linux-media@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Lad Prabhakar <prabhakar.csengg@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: Re: [PATCH] media: ov2659: Fix memleak in ov2659_probe()
Date: Sun, 29 Jun 2025 18:45:28 +0200 [thread overview]
Message-ID: <721cd8f1-1f7d-4f10-bf4d-c75e9d2be8ab@web.de> (raw)
In-Reply-To: <tencent_7745E114F55B42E026AEF67EAB1D6CDBA305@qq.com>
> ov2659_probe() won't clean all the allocated resources in fail
> path, which may causes the memleaks. Add v4l2_ctrl_handler_free() to
> prevent memleak.
Will it be nicer to refer to the term “memory leak” for an improved
change description and summary phrase?
Regards,
Markus
prev parent reply other threads:[~2025-06-29 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 14:49 Zhang Shurong
2025-06-29 16:45 ` Markus Elfring [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=721cd8f1-1f7d-4f10-bf4d-c75e9d2be8ab@web.de \
--to=markus.elfring@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=zhang_shurong@foxmail.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
all inboxes | Powered by JetHome®