LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] drivers/base: cacheinfo: validate device node for all the caches
Date: Mon, 23 Feb 2015 15:14:54 +0000 [thread overview]
Message-ID: <20150223151454.GL9714@leverpostej> (raw)
In-Reply-To: <1424095816-4414-1-git-send-email-sudeep.holla@arm.com>
On Mon, Feb 16, 2015 at 02:10:16PM +0000, Sudeep Holla wrote:
> On architectures that depend on DT for obtaining cache hierarcy, we need
> to validate the device node for all the cache indices, failing to do so
> might result in wrong information being exposed to the userspace.
>
> This is quite possible on initial/incomplete versions of the device
> trees. In such cases, it's better to bail out if all the required device
> nodes are not present.
>
> This patch adds checks for the validation of device node for all the
> caches and doesn't initialise the cacheinfo if there's any error.
>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Reported-by: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---
> drivers/base/cacheinfo.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/base/cacheinfo.c b/drivers/base/cacheinfo.c
> index 6e64563361f0..7015bf05c828 100644
> --- a/drivers/base/cacheinfo.c
> +++ b/drivers/base/cacheinfo.c
> @@ -62,15 +62,21 @@ static int cache_setup_of_node(unsigned int cpu)
> return -ENOENT;
> }
>
> - while (np && index < cache_leaves(cpu)) {
> + while (index < cache_leaves(cpu)) {
> this_leaf = this_cpu_ci->info_list + index;
> if (this_leaf->level != 1)
> np = of_find_next_cache_node(np);
> else
> np = of_node_get(np);/* cpu node itself */
> + if (!np)
> + break;
> this_leaf->of_node = np;
> index++;
> }
> +
> + if (index != cache_leaves(cpu)) /* not all OF nodes populated */
> + return -ENOENT;
> +
> return 0;
> }
>
> @@ -189,8 +195,10 @@ static int detect_cache_attributes(unsigned int cpu)
> * will be set up here only if they are not populated already
> */
> ret = cache_shared_cpu_map_setup(cpu);
> - if (ret)
> + if (ret) {
> + pr_err("failed to setup cache hierarcy from DT\n");
It would probably be better if this were something like:
pr_warn("Unable to detect cache hierarcy from DT for CPU %d\n",
cpu);
Otherwise, this looks sane to me, and it would be nice to have this in
ASAP so as to avoid exposing erroneous information to userspace. So:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Thanks,
Mark.
> goto free_ci;
> + }
> return 0;
>
> free_ci:
> --
> 1.9.1
>
>
next prev parent reply other threads:[~2015-02-23 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 14:10 Sudeep Holla
2015-02-23 15:14 ` Mark Rutland [this message]
2015-02-23 15:45 ` Sudeep Holla
2015-02-23 16:32 ` [PATCH v2] " Sudeep Holla
2015-03-10 9:52 ` Sudeep Holla
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=20150223151454.GL9714@leverpostej \
--to=mark.rutland@arm.com \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudeep.holla@arm.com \
--subject='Re: [PATCH] drivers/base: cacheinfo: validate device node for all the caches' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).