linux-kernel - RE: [PATCH] soundwire: fix usages of device_get_named_child

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CH3PR11MB8436BE8232EAB36C35361A00FF1C2@CH3PR11MB8436.namprd11.prod.outlook.com>
Date: Mon, 6 May 2024 00:48:24 +0000
From: "Liao, Bard" <bard.liao@...el.com>
To: Vinod Koul <vkoul@...nel.org>, Bard Liao <yung-chuan.liao@...ux.intel.com>
CC: "linux-sound@...r.kernel.org" <linux-sound@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"pierre-louis.bossart@...ux.intel.com" <pierre-louis.bossart@...ux.intel.com>
Subject: RE: [PATCH] soundwire: fix usages of device_get_named_child_node()



> -----Original Message-----
> From: Vinod Koul <vkoul@...nel.org>
> Sent: Saturday, May 4, 2024 8:56 PM
> To: Bard Liao <yung-chuan.liao@...ux.intel.com>
> Cc: linux-sound@...r.kernel.org; linux-kernel@...r.kernel.org; pierre-
> louis.bossart@...ux.intel.com; Liao, Bard <bard.liao@...el.com>
> Subject: Re: [PATCH] soundwire: fix usages of device_get_named_child_node()
> 
> On 29-04-24, 00:49, Bard Liao wrote:
> > From: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
> >
> > The documentation for device_get_named_child_node() mentions this
> > important point:
> >
> > "
> > The caller is responsible for calling fwnode_handle_put() on the
> > returned fwnode pointer.
> > "
> >
> > Add fwnode_handle_put() to avoid leaked references.
> 
> This fails on sdw/next for me

Sorry I didn't realize this patch depends on" SoundWire: intel_ace2x:
read DOAIS and DODS from _DSD properties."
Could you please try again now?
Sorry about that.

> 
> --
> ~Vinod