From: Daniel Borkmann <daniel@iogearbox.net>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Quentin Monnet <quentin@isovalent.com>
Cc: Jiri Olsa <olsajiri@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Ian Rogers <irogers@google.com>,
Namhyung Kim <namhyung@kernel.org>,
bpf@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 1/1] bpftool: Be more portable by using POSIX's basename()
Date: Mon, 29 Jan 2024 16:17:00 +0100 [thread overview]
Message-ID: <c23c7c37-8d4e-e9ad-3fa0-a41da3b7aefa@iogearbox.net> (raw)
In-Reply-To: <Zbe3NuOgaupvUcpF@kernel.org>
On 1/29/24 3:33 PM, Arnaldo Carvalho de Melo wrote:
> musl libc had the basename() prototype in string.h, but this is a
> glibc-ism, now they removed the _GNU_SOURCE bits in their devel distro,
> Alpine Linux edge:
>
> https://git.musl-libc.org/cgit/musl/commit/?id=725e17ed6dff4d0cd22487bb64470881e86a92e7
>
> So lets use the POSIX version, the whole rationale is spelled out at:
>
> https://gitlab.alpinelinux.org/alpine/aports/-/issues/15643
>
> Acked-by: Jiri Olsa <olsajiri@gmail.com>
> Acked-by: Quentin Monnet <quentin@isovalent.com>
> Cc: Adrian Hunter <adrian.hunter@intel.com>
> Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>
> Cc: Ian Rogers <irogers@google.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Link: https://lore.kernel.org/lkml/ZZhsPs00TI75RdAr@kernel.org
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> ---
> tools/bpf/bpftool/gen.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/tools/bpf/bpftool/gen.c b/tools/bpf/bpftool/gen.c
> index ee3ce2b8000d75d2..a5cc5938c3d7951e 100644
> --- a/tools/bpf/bpftool/gen.c
> +++ b/tools/bpf/bpftool/gen.c
> @@ -7,6 +7,7 @@
> #include <ctype.h>
> #include <errno.h>
> #include <fcntl.h>
> +#include <libgen.h>
> #include <linux/err.h>
> #include <stdbool.h>
> #include <stdio.h>
> @@ -56,9 +57,10 @@ static bool str_has_suffix(const char *str, const char *suffix)
>
> static void get_obj_name(char *name, const char *file)
> {
> - /* Using basename() GNU version which doesn't modify arg. */
> - strncpy(name, basename(file), MAX_OBJ_NAME_LEN - 1);
> - name[MAX_OBJ_NAME_LEN - 1] = '\0';
> + char file_copy[PATH_MAX];
Added a newline in here while applying, otherwise lgtm, thanks!
> + /* Using basename() POSIX version to be more portable. */
> + strncpy(file_copy, file, PATH_MAX - 1)[PATH_MAX - 1] = '\0';
> + strncpy(name, basename(file_copy), MAX_OBJ_NAME_LEN - 1)[MAX_OBJ_NAME_LEN - 1] = '\0';
> if (str_has_suffix(name, ".o"))
> name[strlen(name) - 2] = '\0';
> sanitize_identifier(name);
>
prev parent reply other threads:[~2024-01-29 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 14:33 [PATCH 1/1] bpftool: Be more portable by using POSIX's basename() Arnaldo Carvalho de Melo
2024-01-29 15:17 ` Daniel Borkmann [this message]
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=c23c7c37-8d4e-e9ad-3fa0-a41da3b7aefa@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=olsajiri@gmail.com \
--cc=quentin@isovalent.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox