All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: "Pierre-Clément Tosi" <ptosi-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Mostafa Saleh <smostafa-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] libfdt: Fix fdt_appendprop_addrrange documentation
Date: Mon, 4 Sep 2023 15:31:01 +1000	[thread overview]
Message-ID: <ZPVrlffenIPXDxJb@zatzit> (raw)
In-Reply-To: <20230831123918.rf54emwkzgtcb7aw-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2513 bytes --]

On Thu, Aug 31, 2023 at 01:39:18PM +0100, Pierre-Clément Tosi wrote:
> According to the documentation, the function should default to the very
> common property name <reg> when none is "specified". However, neither
> passing NULL (ends up calling strlen(NULL) and segfaults) nor ""
> (appends a property with an empty name) implements this behavior.
> 
> Furthermore, the test case supposed to cover this default value actually
> passes the value to the function, somewhat defeating its own purpose:
> 
>     /* 2. default property name */
> 
>     // ...
> 
>     err = fdt_appendprop_addrrange(fdt, 0, offset, "reg", addr, size);
>     if (err)
>             FAIL("Failed to set \"reg\": %s", fdt_strerror(err));
>     check_getprop_addrrange(fdt, 0, offset, "reg", 1);
> 
> Finally, nothing in the implementation of the function seems to attempt
> to cover that use-case.
> 
> As the feature can't ever have been used by clients and as the resulting
> reduced readability of the caller seems (IMO) to outweigh any potential
> benefit this API would bring, remove the erroneous documentation instead
> of trying to fix the function.
> 
> Reported-by: Mostafa Saleh <smostafa-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
> Signed-off-by: Pierre-Clément Tosi <ptosi-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>

Nice catch, and an excellent commit message.

I don't recall this specifically, but my guess would be that an
original draft included that behaviour, but I nixed it during review,
but then both the submitted and I forgot to update the documentation
comments as well.

Merged.

> ---
>  libfdt/libfdt.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/libfdt/libfdt.h b/libfdt/libfdt.h
> index 2a4f32c..0677fea 100644
> --- a/libfdt/libfdt.h
> +++ b/libfdt/libfdt.h
> @@ -2029,7 +2029,7 @@ static inline int fdt_appendprop_cell(void *fdt, int nodeoffset,
>   * address and size) to the value of the named property in the given
>   * node, or creates a new property with that value if it does not
>   * already exist.
> - * If "name" is not specified, a default "reg" is used.
> + *
>   * Cell sizes are determined by parent's #address-cells and #size-cells.
>   *
>   * This function may insert data into the blob, and will therefore

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2023-09-04  5:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31 12:39 [PATCH] libfdt: Fix fdt_appendprop_addrrange documentation Pierre-Clément Tosi
     [not found] ` <20230831123918.rf54emwkzgtcb7aw-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2023-09-04  5:31   ` David Gibson [this message]

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=ZPVrlffenIPXDxJb@zatzit \
    --to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
    --cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ptosi-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=smostafa-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.