Commit 78c44d91 authored by Rhyland Klein's avatar Rhyland Klein Committed by Rob Herring

drivers/of: Fix depth when unflattening devicetree

When the implementation for unflatten_dt_node() changed from being
recursive to being non-recursive, it had a side effect of increasing the
depth passed to fdt_next_node() by 1. This is fine most of the time, but
it seems that when the end of the dtb is being parsed, it will cause the
FDT_END condition in fdt_next_node() to return a different value
(returning nextoffset instead of -FDT_ERR_NOTFOUND). This ends up passing
an FDT_ERR_TRUNCATED error back to the unflatten_dt_node() which then
sees that and complains "Error -8 processing FDT" causing boot to fail.

This patch simply avoids incrementing depth and uses modified accesses
for local array indices so that the depth is the same as it was before
the change as far as fdt_next_node() is concerned.

This problem was discovered trying to boot Tegra210-Smaug platforms.

Fixes: 50800082 ("drivers/of: Avoid recursively calling unflatten_dt_node()")
Signed-off-by: default avatarRhyland Klein <rklein@nvidia.com>
[robh: squashed in KASAN fix from Rhyland]
Signed-off-by: default avatarRob Herring <robh@kernel.org>
parent b9c43856
......@@ -407,24 +407,24 @@ static int unflatten_dt_nodes(const void *blob,
root = dad;
fpsizes[depth] = dad ? strlen(of_node_full_name(dad)) : 0;
nps[depth++] = dad;
nps[depth] = dad;
for (offset = 0;
offset >= 0;
offset >= 0 && depth >= 0;
offset = fdt_next_node(blob, offset, &depth)) {
if (WARN_ON_ONCE(depth >= FDT_MAX_DEPTH))
continue;
fpsizes[depth] = populate_node(blob, offset, &mem,
nps[depth - 1],
fpsizes[depth - 1],
&nps[depth], dryrun);
if (!fpsizes[depth])
fpsizes[depth+1] = populate_node(blob, offset, &mem,
nps[depth],
fpsizes[depth],
&nps[depth+1], dryrun);
if (!fpsizes[depth+1])
return mem - base;
if (!dryrun && nodepp && !*nodepp)
*nodepp = nps[depth];
*nodepp = nps[depth+1];
if (!dryrun && !root)
root = nps[depth];
root = nps[depth+1];
}
if (offset < 0 && offset != -FDT_ERR_NOTFOUND) {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment