From: R Nageswara Sastry <rnsastry@linux.ibm.com>
To: Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
acme@kernel.org, jolsa@kernel.org
Cc: mpe@ellerman.id.au, linux-perf-users@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, maddy@linux.vnet.ibm.com,
kjain@linux.ibm.com
Subject: Re: [PATCH 1/2] tools/perf: Fix out of bound access to affinity "sched_cpus"
Date: Mon, 5 Sep 2022 12:26:27 +0530 [thread overview]
Message-ID: <efe3682b-edb8-b9b2-3c25-3dcf54187702@linux.ibm.com> (raw)
In-Reply-To: <20220905045441.1643-1-atrajeev@linux.vnet.ibm.com>
On 05/09/22 10:24 am, Athira Rajeev wrote:
> The affinity code in "affinity_set" function access array
> named "sched_cpus". The size for this array is allocated in
> affinity_setup function which is nothing but value from
> get_cpu_set_size. This is used to contain the cpumask value
> for each cpu. While setting bit for each cpu, it calls
> "set_bit" function which access index in sched_cpus array.
> If we provide a command-line option to -C which is more than
> the number of CPU's present in the system, the set_bit could
> access an array member which is out-of the array size. This
> is because currently, there is no boundary check for the CPU.
> This will result in seg fault:
>
> <<>>
> ./perf stat -C 12323431 ls
> Perf can support 2048 CPUs. Consider raising MAX_NR_CPUS
> Segmentation fault (core dumped)
> <<>>
>
> Fix this by adding boundary check for the array.
>
> After the fix from powerpc system:
>
> <<>>
> ./perf stat -C 12323431 ls 1>out
> Perf can support 2048 CPUs. Consider raising MAX_NR_CPUS
>
> Performance counter stats for 'CPU(s) 12323431':
>
> <not supported> msec cpu-clock
> <not supported> context-switches
> <not supported> cpu-migrations
> <not supported> page-faults
> <not supported> cycles
> <not supported> instructions
> <not supported> branches
> <not supported> branch-misses
>
> 0.001192373 seconds time elapsed
> <<>>
>
> Reported-by: Nageswara Sastry <rnsastry@linux.ibm.com>
Tested-by: Nageswara Sastry <rnsastry@linux.ibm.com>
> Signed-off-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
> ---
> tools/perf/util/affinity.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/affinity.c b/tools/perf/util/affinity.c
> index 4d216c0dc425..a1dd37347abc 100644
> --- a/tools/perf/util/affinity.c
> +++ b/tools/perf/util/affinity.c
> @@ -49,8 +49,14 @@ void affinity__set(struct affinity *a, int cpu)
> {
> int cpu_set_size = get_cpu_set_size();
>
> - if (cpu == -1)
> + /*
> + * Return:
> + * - if cpu is -1
> + * - restrict out of bound access to sched_cpus
> + */
> + if (cpu == -1 || ((cpu / __BITS_PER_LONG) >= (cpu_set_size / 8)))
> return;
> +
> a->changed = true;
> set_bit(cpu, a->sched_cpus);
> /*
--
Thanks and Regards
R.Nageswara Sastry
next prev parent reply other threads:[~2022-09-05 6:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 4:54 [PATCH 1/2] tools/perf: Fix out of bound access to affinity "sched_cpus" Athira Rajeev
2022-09-05 4:54 ` [PATCH 2/2] tools/perf: Fix out of bound access to cpu mask array Athira Rajeev
2022-09-05 6:56 ` R Nageswara Sastry
2022-09-05 6:56 ` R Nageswara Sastry [this message]
2022-09-05 10:00 ` [PATCH 1/2] tools/perf: Fix out of bound access to affinity "sched_cpus" Jiri Olsa
2022-09-05 11:01 ` Athira Rajeev
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=efe3682b-edb8-b9b2-3c25-3dcf54187702@linux.ibm.com \
--to=rnsastry@linux.ibm.com \
--cc=acme@kernel.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=jolsa@kernel.org \
--cc=kjain@linux.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--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).