From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: sashiko-reviews@lists.linux.dev, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 3/9] perf libbfd: Include the headers that are used
Date: Wed, 16 Sep 2026 10:37:54 -0700 [thread overview]
Message-ID: <aqrT8kgw9ob-ILOj@google.com> (raw)
In-Reply-To: <CAP-5=fWNMrnB9KNjCGOc0A+kwvWWsxYc092x=q6CLK+-g3nwFw@mail.gmail.com>
On Wed, Sep 16, 2026 at 08:54:16AM -0700, Ian Rogers wrote:
> On Tue, Sep 15, 2026 at 11:22 PM <sashiko-bot@kernel.org> wrote:
> >
> > Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> > - [Low] perf libbfd: build failure on musl due to missing <stdarg.h>
> > --
> >
> > commit b4b64b7fbd73cf480fc5aaa2ad17802e8f46fbcc
> > Author: Ian Rogers <irogers@google.com>
> >
> > perf libbfd: Include the headers that are used
> >
> > This patch explicitly includes several POSIX headers directly into libbfd.c
> > instead of relying on indirect inclusions. It also reorders the includes to
> > group system headers before perf's own headers.
> >
> > > diff --git a/tools/perf/util/libbfd.c b/tools/perf/util/libbfd.c
> > > index 131bfedf48cdf..1b23a261a9ced 100644
> > > --- a/tools/perf/util/libbfd.c
> > > +++ b/tools/perf/util/libbfd.c
> > > @@ -1,5 +1,19 @@
> > > // SPDX-License-Identifier: GPL-2.0
> > > #include "libbfd.h"
> > > +
> > > +#include <errno.h>
> > > +#include <inttypes.h>
> > > +#include <limits.h>
> > > +#include <stdint.h>
> > > +#include <stdio.h>
> > > +#include <stdlib.h>
> > > +#include <string.h>
> > > +
> > > +#include <fcntl.h>
> > > +#include <pthread.h>
> > > +
> > > +#include <tools/dis-asm-compat.h>
> >
> > [Severity: Low]
> > Does this inclusion order break the build on musl libc?
> >
> > Because <tools/dis-asm-compat.h> uses va_start and va_end in an inline
> > function, it strictly requires <stdarg.h>. Previously, this requirement
> > was satisfied implicitly because it was included later in the file, after
> > other headers provided the necessary declarations.
> >
> > Moving <tools/dis-asm-compat.h> higher up in the file exposes this missing
> > dependency, which will cause va_start and va_end to be undeclared in strict
> > environments like musl.
> >
> > [ ... ]
>
> I don't plan to fix this as the issue is minor and relates to an
> include, not the code itself. The series has no other Sashiko
> feedback.
> https://sashiko.dev/#/patchset/20260916061218.3061216-1-irogers%40google.com
I think <stdarg.h> should be included by <tools/dis-asm-compat.h> then.
But it looks like a separate issue.
Thanks,
Namhyung
next prev parent reply other threads:[~2026-09-16 17:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 6:12 [PATCH 0/9] perf build: Fix builds with clang and BUILD_NONDISTRO Ian Rogers
2026-09-16 6:12 ` [PATCH 1/9] perf libbfd: Fix the clang -Wthread-safety build failure Ian Rogers
2026-09-16 6:18 ` sashiko-bot
2026-09-16 6:12 ` [PATCH 2/9] perf symbol: Fix the build when demangling with libbfd Ian Rogers
2026-09-16 6:21 ` sashiko-bot
2026-09-16 6:12 ` [PATCH 3/9] perf libbfd: Include the headers that are used Ian Rogers
2026-09-16 6:22 ` sashiko-bot
2026-09-16 15:54 ` Ian Rogers
2026-09-16 17:37 ` Namhyung Kim [this message]
2026-09-16 6:12 ` [PATCH 4/9] perf pmu: " Ian Rogers
2026-09-16 6:14 ` sashiko-bot
2026-09-16 6:12 ` [PATCH 5/9] perf build: Only pass clang flags to CXX when CXX is clang Ian Rogers
2026-09-16 6:17 ` sashiko-bot
2026-09-16 6:12 ` [PATCH 6/9] perf build: Use the given CC rather than clang in clang builds Ian Rogers
2026-09-16 6:19 ` sashiko-bot
2026-09-16 6:12 ` [PATCH 7/9] perf build: Check the version of the compiler that is used Ian Rogers
2026-09-16 6:16 ` sashiko-bot
2026-09-16 6:12 ` [PATCH 8/9] perf build: Remove leftovers of removed build options Ian Rogers
2026-09-16 6:17 ` sashiko-bot
2026-09-16 6:12 ` [PATCH 9/9] perf test: Add build tests for clang and libbfd demangling Ian Rogers
2026-09-16 6:22 ` sashiko-bot
2026-09-16 17:35 ` [PATCH 0/9] perf build: Fix builds with clang and BUILD_NONDISTRO Namhyung Kim
2026-09-22 12:47 ` Arnaldo Carvalho de Melo
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=aqrT8kgw9ob-ILOj@google.com \
--to=namhyung@kernel.org \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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