lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <721cd8f1-1f7d-4f10-bf4d-c75e9d2be8ab@web.de>
Date: Sun, 29 Jun 2025 18:45:28 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Zhang Shurong <zhang_shurong@...mail.com>, linux-media@...r.kernel.org
Cc: LKML <linux-kernel@...r.kernel.org>,
 Lad Prabhakar <prabhakar.csengg@...il.com>,
 Mauro Carvalho Chehab <mchehab@...nel.org>,
 Sakari Ailus <sakari.ailus@...ux.intel.com>
Subject: Re: [PATCH] media: ov2659: Fix memleak in ov2659_probe()

> 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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ