From: David Gibson <david@gibson.dropbear.id.au>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Jonathan Marler <johnnymarler@gmail.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Alexander Graf <agraf@suse.de>,
QEMU Developers <qemu-devel@nongnu.org>,
QEMU Trivial <qemu-trivial@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] handle all fdt_get_phandle_errors
Date: Wed, 13 Jun 2018 20:34:02 +1000 [thread overview]
Message-ID: <20180613103402.GM30690@umbus.fritz.box> (raw)
In-Reply-To: <CAFEAcA-nnU2E6CKPiGqoAq1sSYtvf4Hxp3MtYiCvigr4i8-+Ow@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2237 bytes --]
On Mon, May 14, 2018 at 04:56:54PM +0100, Peter Maydell wrote:
> On 4 May 2018 at 19:37, Jonathan Marler <johnnymarler@gmail.com> wrote:
> > Signed-off-by: Jonathan Marler <johnnymarler@gmail.com>
>
> Hi; thanks for this patch.
>
> > ---
> > device_tree.c | 8 ++++++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/device_tree.c b/device_tree.c
> > index 52c3358..2b75905 100644
> > --- a/device_tree.c
> > +++ b/device_tree.c
> > @@ -379,8 +379,12 @@ uint32_t qemu_fdt_get_phandle(void *fdt, const char
> > *path)
> >
> > r = fdt_get_phandle(fdt, findnode_nofail(fdt, path));
> > if (r == 0) {
> > - error_report("%s: Couldn't get phandle for %s: %s", __func__,
> > - path, fdt_strerror(r));
> > + error_report("%s: Node %s does not have a 'phandle'", __func__,
> > + path);
> > + exit(1);
> > + }
> > + if (r == -1) {
> > + error_report("%s: Couldn't get phandle for %s", __func__, path);
> > exit(1);
> > }
>
> Could you explain in what situation this is needed? The documentation
> for fdt_get_phandle() says
> * returns:
> * the phandle of the node at nodeoffset, on success (!= 0, != -1)
> * 0, if the node has no phandle, or another error occurs
>
> which I interpret to mean that it is not possible for it to return -1.
I *think* that was the intention; it's a long time since I wrote it,
so I'm not sure. However, looking at the implementation, that's not
strictly the case.
We certainly return 0 for any error we explicitly detect. However, if
the node has a "phandle" property that's correctly formed but contains
-1, then we'll return -1. Of course, a correct dt blob won't have
such a property, but then we do detect a bunch of other conditions
that a correct dt shouldn't have.
On balance, I'm thinking I should probably change libfdt to check for
a -1 phandle property and return 0 for that case, like all other error
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:[~2018-06-13 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 18:37 [Qemu-devel] [PATCH] handle all fdt_get_phandle_errors Jonathan Marler
2018-05-14 15:56 ` Stefan Hajnoczi
2018-05-14 15:56 ` Peter Maydell
2018-06-13 10:34 ` 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=20180613103402.GM30690@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=crosthwaite.peter@gmail.com \
--cc=johnnymarler@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).