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
| ||
|
Message-ID: <Y6wOS8NFAZc5+piJ@smile.fi.intel.com> Date: Wed, 28 Dec 2022 11:37:15 +0200 From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com> To: Yang Yingliang <yangyingliang@...wei.com> Cc: linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org, djrscally@...il.com, heikki.krogerus@...ux.intel.com, sakari.ailus@...ux.intel.com, gregkh@...uxfoundation.org, rafael@...nel.org Subject: Re: [PATCH v3] device property: fix of node refcount leak in fwnode_graph_get_next_endpoint() On Wed, Nov 23, 2022 at 10:25:42AM +0800, Yang Yingliang wrote: > The 'parent' returned by fwnode_graph_get_port_parent() > with refcount incremented when 'prev' is not NULL, it > needs be put when finish using it. > > Because the parent is const, introduce a new variable to > store the returned fwnode, then put it before returning > from fwnode_graph_get_next_endpoint(). Rafael, Greg, is this went through the cracks? -- With Best Regards, Andy Shevchenko
Powered by blists - more mailing lists