From: "Clément Léger" <clement.leger@bootlin•com>
To: Rob Herring <robh@kernel•org>
Cc: Nathan Lynch <nathanl@linux•ibm.com>,
devicetree@vger•kernel.org, Ohhoon Kwon <ohoono.kwon@samsung•com>,
David Hildenbrand <david@redhat•com>,
Steen Hegelund <steen.hegelund@microchip•com>,
Daniel Henrique Barboza <danielhb413@gmail•com>,
YueHaibing <yuehaibing@huawei•com>,
linuxppc-dev@lists•ozlabs.org, linux-kernel@vger•kernel.org,
Paul Mackerras <paulus@samba•org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux•ibm.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin•com>,
Allan Nielsen <allan.nielsen@microchip•com>,
Andrew Morton <akpm@linux-foundation•org>,
Laurent Dufour <ldufour@linux•ibm.com>,
Frank Rowand <frowand.list@gmail•com>,
Horatiu Vultur <horatiu.vultur@microchip•com>,
David Gibson <david@gibson•dropbear.id.au>
Subject: Re: [PATCH 1/3] of: dynamic: add of_property_alloc() and of_property_free()
Date: Fri, 6 May 2022 09:49:05 +0200 [thread overview]
Message-ID: <20220506094905.27bc99aa@fixe.home> (raw)
In-Reply-To: <YnQnayouXw9/jp/E@robh.at.kernel.org>
Le Thu, 5 May 2022 14:37:15 -0500,
Rob Herring <robh@kernel•org> a écrit :
> > +
> > +/**
> > + * of_property_alloc - Allocate a property dynamically.
> > + * @name: Name of the new property
> > + * @value: Value that will be copied into the new property value
> > + * @value_len: length of @value to be copied into the new property value
> > + * @len: Length of new property value, must be greater than @value_len
>
> What's the usecase for the lengths being different? That doesn't seem
> like a common case, so perhaps handle it with a NULL value and
> non-zero length. Then the caller has to deal with populating
> prop->value.
That was actually something used by powerpc code but agreed, letting
the user recopy it's values seems fine to me and the usage will be more
clear.
> > /*
> > - * NOTE: There is no check for zero length value.
> > - * In case of a boolean property, this will allocate a value
> > - * of zero bytes. We do this to work around the use
> > - * of of_get_property() calls on boolean values.
> > + * Even if the property has no value, it must be set to a
> > + * non-null value since of_get_property() is used to check
> > + * some values that might or not have a values (ranges for
> > + * instance). Moreover, when the node is released, prop->value
> > + * is kfreed so the memory must come from kmalloc.
>
> Allowing for NULL value didn't turn out well...
>
> We know that we can do the kfree because OF_DYNAMIC is set IIRC...
>
> If we do 1 allocation for prop and value, then we can test
> for "prop->value == prop + 1" to determine if we need to free or not.
Sounds like a good idea.
--
Clément Léger,
Embedded Linux and Kernel engineer at Bootlin
https://bootlin.com
next prev parent reply other threads:[~2022-05-06 7:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 15:40 [PATCH 0/3] of: add of_property_alloc/free() and of_node_alloc/free() Clément Léger
2022-05-04 15:40 ` [PATCH 1/3] of: dynamic: add of_property_alloc() and of_property_free() Clément Léger
2022-05-05 7:30 ` Christophe Leroy
2022-05-05 9:47 ` Clément Léger
2022-05-05 17:37 ` Rob Herring
2022-05-06 7:43 ` Clément Léger
2022-05-05 19:37 ` Rob Herring
2022-05-06 7:49 ` Clément Léger [this message]
2022-06-01 22:30 ` Tyrel Datwyler
2022-06-02 14:06 ` Rob Herring
2022-06-02 18:07 ` Tyrel Datwyler
2022-05-04 15:40 ` [PATCH 2/3] of: dynamic: add of_node_alloc() and of_node_free() Clément Léger
2022-05-05 7:32 ` Christophe Leroy
2022-05-05 19:43 ` Rob Herring
2022-05-06 10:43 ` Clément Léger
2022-05-09 16:55 ` Rob Herring
2022-05-04 15:40 ` [PATCH 3/3] powerpc/pseries: use of_property_*() and of_node_*() functions Clément Léger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220506094905.27bc99aa@fixe.home \
--to=clement.leger@bootlin$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=allan.nielsen@microchip$(echo .)com \
--cc=aneesh.kumar@linux$(echo .)ibm.com \
--cc=danielhb413@gmail$(echo .)com \
--cc=david@gibson$(echo .)dropbear.id.au \
--cc=david@redhat$(echo .)com \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=frowand.list@gmail$(echo .)com \
--cc=horatiu.vultur@microchip$(echo .)com \
--cc=ldufour@linux$(echo .)ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=nathanl@linux$(echo .)ibm.com \
--cc=ohoono.kwon@samsung$(echo .)com \
--cc=paulus@samba$(echo .)org \
--cc=robh@kernel$(echo .)org \
--cc=steen.hegelund@microchip$(echo .)com \
--cc=thomas.petazzoni@bootlin$(echo .)com \
--cc=yuehaibing@huawei$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox