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]
Date:   Fri, 29 Mar 2019 17:31:57 +0200
From:   Sakari Ailus <>
To:     Andy Shevchenko <>
Cc:     Petr Mladek <>,,,,, Rob Herring <>
Subject: Re: [PATCH v2 1/6] device property: Add functions for accessing
 node's parents

Hi Andy,

On Fri, Mar 29, 2019 at 04:14:19PM +0200, Andy Shevchenko wrote:
> On Fri, Mar 29, 2019 at 03:04:36PM +0200, Sakari Ailus wrote:
> > On Thu, Mar 28, 2019 at 03:10:36PM +0100, Petr Mladek wrote:
> > You basically have to have a reference to a node until you're done
> > accessing it. The refcounting in the fwnode framework is based on the OF
> > API --- otherwise you couldn't access OF nodes using the framework.
> > ACPI
> > does not have those (as you can't dynamically remove nodes).
> What about configfs where we can load / unload tables at run time?

Hmm. I have to admit I missed this one.

Well, I guess that this feature depends on the user making sure there are
no references to the tables that are to be removed, as there is no
refcounting. Let me know if I'm missing something, but nothing appears to
prevent releasing nodes that are in use.

If that is really so, then refcounting or another mechanism to achieve
something similar should be added to make removal safe, but this isn't
related to printing the node names anymore nor such fixes belong to this


Sakari Ailus

Powered by blists - more mailing lists