From: David Gibson <david@gibson.dropbear.id.au>
To: "Pierre-Clément Tosi" <ptosi@google.com>
Cc: devicetree-compiler@vger.kernel.org
Subject: Re: [PATCH] libfdt: fdt_path_offset_namelen: Reject empty path
Date: Sun, 8 Oct 2023 13:32:29 +1100 [thread overview]
Message-ID: <ZSIUvZxNh7OuZD3/@zatzit> (raw)
In-Reply-To: <20231006124839.z7auhc3mk37gxios@google.com>
[-- Attachment #1: Type: text/plain, Size: 1751 bytes --]
On Fri, Oct 06, 2023 at 01:48:39PM +0100, Pierre-Clément Tosi wrote:
> Make empty paths result in FDT_ERR_BADPATH.
>
> Per the specification (v0.4-rc4):
>
> > The convention for specifying a device path is:
> > /node-name-1/node-name-2/node-name-N
> >
> > The path to the root node is /.
> >
> > A unit address may be omitted if the full path to the
> > node is unambiguous.
As Rob noted, I don't really see how this quote is relevant to the
change at hand.
The change itself looks like a good idea, though. Without this, we
will at the very least do a one byte bad access in the next line. If
someone does path a negative value it will do... something bad,
probably.
> Signed-off-by: Pierre-Clément Tosi <ptosi@google.com>
> ---
> libfdt/fdt_ro.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/libfdt/fdt_ro.c b/libfdt/fdt_ro.c
> index c4c520c..46b4ef5 100644
> --- a/libfdt/fdt_ro.c
> +++ b/libfdt/fdt_ro.c
> @@ -255,6 +255,9 @@ int fdt_path_offset_namelen(const void *fdt, const char *path, int namelen)
>
> FDT_RO_PROBE(fdt);
>
> + if (namelen < 1)
> + return -FDT_ERR_BADPATH;
It would be better to make this:
if (!can_assume(VALID_INPUT) && namelen <= 0)
This allows the test to be optimised out in builds where we can assume
always valid parameters.
> /* see if we have an alias */
> if (*path != '/') {
> const char *q = memchr(path, '/', end - p);
It would also be really nice to add a testcase for behaviour in the
namelen == 0 and namelen < 0 cases.
--
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 --]
prev parent reply other threads:[~2023-10-08 2:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 12:48 [PATCH] libfdt: fdt_path_offset_namelen: Reject empty path Pierre-Clément Tosi
2023-10-06 13:22 ` Simon Glass
2023-10-07 11:17 ` Pierre-Clément Tosi
2023-10-08 2:32 ` David Gibson
2023-10-06 14:06 ` Rob Herring
2023-10-06 22:42 ` Simon Glass
2023-10-07 11:21 ` Pierre-Clément Tosi
2023-10-08 2:32 ` 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=ZSIUvZxNh7OuZD3/@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=devicetree-compiler@vger.kernel.org \
--cc=ptosi@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox