From: Namhyung Kim <namhyung@kernel.org>
To: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Cc: acme@kernel.org, jolsa@kernel.org, adrian.hunter@intel.com,
irogers@google.com, linux-perf-users@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, akanksha@linux.ibm.com,
maddy@linux.ibm.com, kjain@linux.ibm.com,
disgoel@linux.vnet.ibm.com, hbathini@linux.ibm.com
Subject: Re: [PATCH] tools/perf/tests: Fix compilation error with strncpy in tests/tool_pmu
Date: Mon, 14 Oct 2024 10:26:53 -0700 [thread overview]
Message-ID: <Zw1UXbWTS9Gk3lmw@google.com> (raw)
In-Reply-To: <20241013173742.71882-1-atrajeev@linux.vnet.ibm.com>
Hello Athira,
On Sun, Oct 13, 2024 at 11:07:42PM +0530, Athira Rajeev wrote:
> perf fails to compile on systems with GCC version11
> as below:
>
> In file included from /usr/include/string.h:519,
> from /home/athir/perf-tools-next/tools/include/linux/bitmap.h:5,
> from /home/athir/perf-tools-next/tools/perf/util/pmu.h:5,
> from /home/athir/perf-tools-next/tools/perf/util/evsel.h:14,
> from /home/athir/perf-tools-next/tools/perf/util/evlist.h:14,
> from tests/tool_pmu.c:3:
> In function ‘strncpy’,
> inlined from ‘do_test’ at tests/tool_pmu.c:25:3:
> /usr/include/bits/string_fortified.h:95:10: error: ‘__builtin_strncpy’ specified bound 128 equals destination size [-Werror=stringop-truncation]
> 95 | return __builtin___strncpy_chk (__dest, __src, __len,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 96 | __glibc_objsize (__dest));
> | ~~~~~~~~~~~~~~~~~~~~~~~~~
>
> The compile error is from strncpy refernce in do_test:
> strncpy(str, tool_pmu__event_to_str(ev), sizeof(str));
>
> This behaviour is not observed with GCC version 8, but observed
> with GCC version 11 . This is message from gcc for detecting
> truncation while using strncpu. Use snprintf instead of strncpy
> here to be safe.
>
> Signed-off-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
I found this issue now and thanks for the quick fix. I will push to
perf-tools-next soon.
Thanks,
Namhyung
> ---
> tools/perf/tests/tool_pmu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/tests/tool_pmu.c b/tools/perf/tests/tool_pmu.c
> index 94d0dd8fd3cb..297cc8c55579 100644
> --- a/tools/perf/tests/tool_pmu.c
> +++ b/tools/perf/tests/tool_pmu.c
> @@ -22,7 +22,7 @@ static int do_test(enum tool_pmu_event ev, bool with_pmu)
> if (with_pmu)
> snprintf(str, sizeof(str), "tool/%s/", tool_pmu__event_to_str(ev));
> else
> - strncpy(str, tool_pmu__event_to_str(ev), sizeof(str));
> + snprintf(str, sizeof(str), "%s", tool_pmu__event_to_str(ev));
>
> parse_events_error__init(&err);
> ret = parse_events(evlist, str, &err);
> --
> 2.43.5
>
next prev parent reply other threads:[~2024-10-14 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 17:37 [PATCH] tools/perf/tests: Fix compilation error with strncpy in tests/tool_pmu Athira Rajeev
2024-10-14 17:26 ` Namhyung Kim [this message]
2024-10-16 12:29 ` Athira Rajeev
2024-10-16 15:06 ` Ian Rogers
2024-10-16 18:23 ` Athira Rajeev
2024-10-16 19:04 ` Ian Rogers
2024-10-14 17:38 ` Namhyung Kim
2024-10-14 17:43 ` Namhyung Kim
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=Zw1UXbWTS9Gk3lmw@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=akanksha@linux.ibm.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=disgoel@linux.vnet.ibm.com \
--cc=hbathini@linux.ibm.com \
--cc=irogers@google.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.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.