summaryrefslogtreecommitdiff
path: root/fs/xfs/uuid.c
diff options
context:
space:
mode:
authorWladislav Wiebe <wladislav.kw@gmail.com>2013-08-12 11:06:53 (GMT)
committerRob Herring <rob.herring@calxeda.com>2013-08-22 01:05:49 (GMT)
commit9e40127526e857fa3f29d51e83277204fbdfc6ba (patch)
treec7f94d005ddfa9edbc41feabb2bf44f651af633f /fs/xfs/uuid.c
parentd4e4ab86bcba5a72779c43dc1459f71fea3d89c8 (diff)
downloadlinux-9e40127526e857fa3f29d51e83277204fbdfc6ba.tar.xz
of: fdt: fix memory initialization for expanded DT
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> Cc: stable@vger.kernel.org Signed-off-by: Rob Herring <rob.herring@calxeda.com>
Diffstat (limited to 'fs/xfs/uuid.c')
0 files changed, 0 insertions, 0 deletions