From: Alexander Sverdlin <alexander.sverdlin@nsn.com>
To: ext Wladislav Wiebe <wladislav.kw@gmail.com>
Cc: grant.likely@linaro.org, rob.herring@calxeda.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] of: fdt: fix memory initialization for expanded DT
Date: Fri, 16 Aug 2013 14:30:26 +0200 [thread overview]
Message-ID: <520E1B62.1060501@nsn.com> (raw)
In-Reply-To: <5208C04A.5000303@gmail.com>
Hi!
On 08/12/2013 01:00 PM, ext Wladislav Wiebe wrote:
> Already existing property flags are filled wrong for properties created from
> initial FDT. This could cause problems if this DYNAMIC device-tree functions
> are used later, i.e. properties are attached/detached/replaced. Simply dumping
> flags from the running system show, that some initial static (not allocated via
> kzmalloc()) nodes are marked as dynamic.
>
> I putted some debug extensions to property_proc_show(..) :
> ..
> + if (OF_IS_DYNAMIC(pp))
> + pr_err("DEBUG: xxx : OF_IS_DYNAMIC\n");
> + if (OF_IS_DETACHED(pp))
> + pr_err("DEBUG: xxx : OF_IS_DETACHED\n");
>
> when you operate on the nodes (e.g.: ~$ cat /proc/device-tree/*some_node*) you
> will see that those flags are filled wrong, basically in most cases it will dump
> a DYNAMIC or DETACHED status, which is in not true.
> (BTW. this OF_IS_DETACHED is a own define for debug purposes which which just
> make a test_bit(OF_DETACHED, &x->_flags)
>
> If nodes are dynamic kernel is allowed to kfree() them. But it will crash
> attempting to do so on the nodes from FDT -- they are not allocated via
> kzmalloc().
>
> Signed-off-by: Wladislav Wiebe <wladislav.kw@gmail.com>
Acked-by: Alexander Sverdlin <alexander.sverdlin@nsn.com>
> ---
> drivers/of/fdt.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
> index 6bb7cf2..b10ba00 100644
> --- a/drivers/of/fdt.c
> +++ b/drivers/of/fdt.c
> @@ -392,6 +392,8 @@ static void __unflatten_device_tree(struct boot_param_header *blob,
> mem = (unsigned long)
> dt_alloc(size + 4, __alignof__(struct device_node));
>
> + memset((void *)mem, 0, size);
> +
> ((__be32 *)mem)[size / 4] = cpu_to_be32(0xdeadbeef);
>
> pr_debug(" unflattening %lx...\n", mem);
>
--
Best regards,
Alexander Sverdlin.
next prev parent reply other threads:[~2013-08-16 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 11:00 Wladislav Wiebe
2013-08-16 12:30 ` Alexander Sverdlin [this message]
2013-08-28 20:21 ` Grant Likely
2013-08-28 20:24 ` Grant Likely
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=520E1B62.1060501@nsn.com \
--to=alexander.sverdlin@nsn.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=wladislav.kw@gmail.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
Powered by JetHome