From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: Namhyung Kim <namhyung@kernel.org>, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 1/3] perf trace: Include copied headers in the beauty directory
Date: Mon, 25 May 2026 12:45:20 -0300 [thread overview]
Message-ID: <ahRukLitz4NR6lMC@x1> (raw)
In-Reply-To: <20260525013129.F04641F000E9@smtp.kernel.org>
On Mon, May 25, 2026 at 01:31:29AM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] The copied UAPI header `fcntl.h` includes `<linux/openat2.h>`, which was not copied into the `tools/include/uapi/linux/` directory, causing build failures on older host systems.
> --
>
> commit 7bb011deeef80e2496028a3477432fac108a240f
> Author: Namhyung Kim <namhyung@kernel.org>
>
> perf trace: Include copied headers in the beauty directory
>
> This commit updates the trace beauty scripts to use local copies of UAPI
> kernel headers directly, rather than relying on system headers or manual
> macro definitions.
>
> > diff --git a/tools/perf/trace/beauty/fcntl.c b/tools/perf/trace/beauty/fcntl.c
> > index e1b99b8f55eb0..10fd6a2b75c35 100644
> > --- a/tools/perf/trace/beauty/fcntl.c
> > +++ b/tools/perf/trace/beauty/fcntl.c
> [ ... ]
> > -#include "trace/beauty/beauty.h"
> > #include <linux/kernel.h>
> > -#include <linux/fcntl.h>
> [ ... ]
> > +#include "trace/beauty/beauty.h"
> > +#include "trace/beauty/include/uapi/linux/fcntl.h"
>
> [Severity: Low]
> Will this cause a build failure on systems with older kernel headers?
>
> The newly copied uapi/linux/fcntl.h includes <linux/openat2.h>, but it
> appears openat2.h was not copied into the tools directory. On build
> environments with kernel headers older than v5.6, the compiler will fall
> back to the host system's include paths, fail to find linux/openat2.h,
> and halt the build.
>
> Should linux/openat2.h also be copied into the tools include directory to
> prevent this?
So, this is exactly the kind of dependencies I mentioned in my reply to
you :-)
- Arnaldo
next prev parent reply other threads:[~2026-05-25 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 1:11 [PATCH 1/3] perf trace: Include copied headers in the beauty directory Namhyung Kim
2026-05-25 1:11 ` [PATCH 2/3] perf trace: Copy uapi/linux/eventfd.h for beautifier Namhyung Kim
2026-05-25 1:11 ` [PATCH 3/3] perf trace: Copy uapi/linux/futex.h " Namhyung Kim
2026-05-25 1:31 ` [PATCH 1/3] perf trace: Include copied headers in the beauty directory sashiko-bot
2026-05-25 15:45 ` Arnaldo Carvalho de Melo [this message]
2026-05-25 11:46 ` Arnaldo Carvalho de Melo
2026-05-26 0:14 ` 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=ahRukLitz4NR6lMC@x1 \
--to=acme@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@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 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.