Re: [RFC PATCH 51/77] dtc: Avoid NULL fullpath for nodes in orphan trees

[Herve Codina <herve.codina@bootlin.com>]

On Thu, 15 Jan 2026 17:56:07 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:

> On Mon, Jan 12, 2026 at 03:19:41PM +0100, Herve Codina wrote:
> > Orphan nodes have been introduced recently.
> > 
> > The process_checks() function uses fullpath in several places and
> > crashes due NULL pointer dereferences if fullpath is NULL.
> > 
> > In order to have process_checks() function running without crashes with
> > orphan trees (i.e. trees based on orphan nodes), the fullpath of node
> > available in those orphan trees must not be NULL.
> > 
> > Fullpath values are built by dti_fill_fullpaths(). Update it to handle
> > fullpath in trees based on orphan nodes.
> > 
> > Use a simple "__orphan__/" prefix to avoid the NULL pointer and to be
> > distinct from the root node ("/" prefix).
> > 
> > It is worth noting that this "__orphan__/" prefix is a temporary prefix
> > and it will be change later when support for reference by path involving
> > nodes in orphan tree is added.  
> 
> It might be simpler to eliminate the fullpath field entirely, and
> instead have a function that calculates fullpaths at the point you
> need them.

I am not sure it will be simpler.

I would prefer keeping dti_fill_fullpaths() for the moment.

This could be change later when things are more stable.

Many thinks are under discussion and changing all users of the the fullpath
field now will introduce more complexity which is not needed right now.

Best regards,
Hervé