From: Sascha Hauer <s.hauer@pengutronix.de>
To: Pascal Vizeli <pvizeli@syshack.ch>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/1] drivers: of: bugfix partition fixups
Date: Fri, 8 Jun 2018 09:05:40 +0200 [thread overview]
Message-ID: <20180608070540.m6etfu37vu6s64ic@pengutronix.de> (raw)
In-Reply-To: <20180607174011.13130-1-pvizeli@syshack.ch>
On Thu, Jun 07, 2018 at 05:40:11PM +0000, Pascal Vizeli wrote:
> If we load a new device tree for linux kernel with a diferent layout,
> the fixup of partition going into endless loop. Exactly the of_find_property
> function will never come back on a invalid device_node.
of_find_property is not called directly from the code you are changing,
so how excatly is the code path that fails?
>
> My patch check, if the device will exists on device tree before we run the
> fixup.
>
> Signed-off-by: Pascal Vizeli <pvizeli@syshack.ch>
> ---
> drivers/of/partition.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/of/partition.c b/drivers/of/partition.c
> index aa6e601b7..17e420964 100644
> --- a/drivers/of/partition.c
> +++ b/drivers/of/partition.c
> @@ -140,6 +140,9 @@ static int of_partition_fixup(struct device_node *root, void *ctx)
> if (!cdev->device_node)
> return -EINVAL;
>
> + if (!of_find_node_by_path(cdev->device_node->full_name))
> + return -EINVAL;
> +
What are you doing to get into this situation? This test should never
fail or else we are in trouble. Is there some "oftree -f" command
involved? I should really remove this command since in a device tree
based system there are always references to device nodes which are not
expected to become invalid.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-06-08 7:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 17:40 Pascal Vizeli
2018-06-08 7:05 ` Sascha Hauer [this message]
2018-06-08 7:31 ` Pascal Vizeli
2018-06-11 6:41 ` Sascha Hauer
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=20180608070540.m6etfu37vu6s64ic@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=pvizeli@syshack.ch \
/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