From: Christian Kujau <lists@nerdbynature.de>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, monstr@monstr.eu,
microblaze-uclinux@itee.uq.edu.au,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] device-tree: Drop properties with "/" in their name
Date: Sun, 13 Jun 2010 00:47:20 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.01.1006130045230.3964@bogon.housecafe.de> (raw)
In-Reply-To: <0958c243b32f5f77028a794a9ce0d55f9a12121e.1274272289.git.michael@ellerman.id.au>
On Wed, 19 May 2010 at 22:32, Michael Ellerman wrote:
> Some bogus firmwares include properties with "/" in their name. This
> causes problems when creating the /proc/device-tree file system,
> because the slash is taken to indicate a directory.
>
> We don't care about those properties, and we don't want to encourage
> them, so just throw them away when creating /proc/device-tree.
>
> Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
> ---
>
> Hi Christian, if you could test this new patch that'd be great, thanks!
I've tested the patch, the Badness is gone and the system is stable as
ever. Will this be pushed to 2.6.35?
Thanks,
Christian.
> fs/proc/proc_devtree.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/fs/proc/proc_devtree.c b/fs/proc/proc_devtree.c
> index ce94801..d9396a4 100644
> --- a/fs/proc/proc_devtree.c
> +++ b/fs/proc/proc_devtree.c
> @@ -209,6 +209,9 @@ void proc_device_tree_add_node(struct device_node *np,
> for (pp = np->properties; pp != NULL; pp = pp->next) {
> p = pp->name;
>
> + if (strchr(p, '/'))
> + continue;
> +
> if (duplicate_name(de, p))
> p = fixup_name(np, de, p);
>
> --
> 1.7.0.4
>
>
>
--
BOFH excuse #334:
50% of the manual is in .pdf readme files
next parent reply other threads:[~2010-06-13 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0958c243b32f5f77028a794a9ce0d55f9a12121e.1274272289.git.michael@ellerman.id.au>
2010-06-13 7:47 ` Christian Kujau [this message]
2010-06-13 8:15 ` Michael Ellerman
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=alpine.DEB.2.01.1006130045230.3964@bogon.housecafe.de \
--to=lists@nerdbynature.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=monstr@monstr.eu \
/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
all inboxes | Powered by JetHome®