linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
To: Anju T Sudhakar <anju@linux.vnet.ibm.com>, mpe@ellerman.id.au
Cc: linuxppc-dev@lists.ozlabs.org, dan.carpenter@oracle.com
Subject: Re: [PATCH v2] powerpc/perf: Fix loop exit condition in nest_imc_event_init
Date: Wed, 19 Dec 2018 11:23:15 +0530	[thread overview]
Message-ID: <6b099a80-6ba9-b7cc-25ed-a038f5b273a7@linux.vnet.ibm.com> (raw)
In-Reply-To: <20181218062041.25198-1-anju@linux.vnet.ibm.com>


On 18/12/18 11:50 AM, Anju T Sudhakar wrote:
> The data structure (i.e struct imc_mem_info) to hold the memory address
> information for nest imc units is allocated based on the number of nodes
> in the system.
>
> nest_imc_event_init() traverse this struct array to calculate the memory
> base address for the event-cpu. If we fail to find a match for the event
> cpu's chip-id in imc_mem_info struct array, then the do-while loop will
> iterate until we crash.
>
> Fix this by changing the loop exit condition based on the number of
> non zero vbase elements in the array, since the allocation is done for
> nr_chips + 1.

Reviewed-by: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>

B/w we will also need this patch to go along
https://patchwork.ozlabs.org/patch/1003669/

These 2 fixes need to go to stable also.

> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Fixes: 885dcd709ba91 ( powerpc/perf: Add nest IMC PMU support)
> Signed-off-by: Anju T Sudhakar <anju@linux.vnet.ibm.com>
> ---
>   arch/powerpc/perf/imc-pmu.c               | 2 +-
>   arch/powerpc/platforms/powernv/opal-imc.c | 2 +-
>   2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/perf/imc-pmu.c b/arch/powerpc/perf/imc-pmu.c
> index 4f34c75..d1009fe 100644
> --- a/arch/powerpc/perf/imc-pmu.c
> +++ b/arch/powerpc/perf/imc-pmu.c
> @@ -508,7 +508,7 @@ static int nest_imc_event_init(struct perf_event *event)
>   			break;
>   		}
>   		pcni++;
> -	} while (pcni);
> +	} while (pcni->vbase != 0);
>
>   	if (!flag)
>   		return -ENODEV;
> diff --git a/arch/powerpc/platforms/powernv/opal-imc.c b/arch/powerpc/platforms/powernv/opal-imc.c
> index 58a0794..3d27f02 100644
> --- a/arch/powerpc/platforms/powernv/opal-imc.c
> +++ b/arch/powerpc/platforms/powernv/opal-imc.c
> @@ -127,7 +127,7 @@ static int imc_get_mem_addr_nest(struct device_node *node,
>   								nr_chips))
>   		goto error;
>
> -	pmu_ptr->mem_info = kcalloc(nr_chips, sizeof(*pmu_ptr->mem_info),
> +	pmu_ptr->mem_info = kcalloc(nr_chips + 1, sizeof(*pmu_ptr->mem_info),
>   				    GFP_KERNEL);
>   	if (!pmu_ptr->mem_info)
>   		goto error;


  reply	other threads:[~2018-12-19  5:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18  6:20 [PATCH v2] powerpc/perf: Fix loop exit condition in nest_imc_event_init Anju T Sudhakar
2018-12-19  5:53 ` Madhavan Srinivasan [this message]
2019-05-03  6:59 ` 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=6b099a80-6ba9-b7cc-25ed-a038f5b273a7@linux.vnet.ibm.com \
    --to=maddy@linux.vnet.ibm.com \
    --cc=anju@linux.vnet.ibm.com \
    --cc=dan.carpenter@oracle.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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;
as well as URLs for NNTP newsgroup(s).