From: sashiko-bot@kernel.org
To: "Namhyung Kim" <namhyung@kernel.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 3/5] perf trace: Sync uapi/linux/mount.h with the kernel source
Date: Mon, 04 May 2026 19:33:29 +0000 [thread overview]
Message-ID: <20260504193332.01FC6C2BCB8@smtp.kernel.org> (raw)
In-Reply-To: <20260503193137.27465-4-namhyung@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The commit syncs `uapi/linux/mount.h` to pick up the `FSMOUNT_NAMESPACE` flag, with the commit message explicitly claiming "This would be used to beautify mount syscall arguments". However, unlike `MOUNT_ATTR_*` flags which are automatically parsed by `tools/perf/trace/beauty/fsmount.sh`, the `FSMOUNT_*` flags are strictly hardcoded in `tools/perf/builtin-trace.c` (`static const char *fsmount_flags[] = { [1] = "CLOEXEC", };`). Because `[2] = "NAMESPACE"` was not manually added to this array, the new flag will not be beautified.
--
commit 41bba49a1df4092fb9de0814ee5b9c785fd42578
Author: Namhyung Kim <namhyung@kernel.org>
perf trace: Sync uapi/linux/mount.h with the kernel source
This commit syncs the uapi/linux/mount.h header to pick up the new
FSMOUNT_NAMESPACE flag.
> diff --git a/tools/perf/trace/beauty/include/uapi/linux/mount.h b/tools/perf/trace/beauty/include/uapi/linux/mount.h
> index d9d86598d100..2204708dbf7a 100644
> --- a/tools/perf/trace/beauty/include/uapi/linux/mount.h
> +++ b/tools/perf/trace/beauty/include/uapi/linux/mount.h
> @@ -110,6 +110,7 @@ enum fsconfig_command {
> * fsmount() flags.
> */
> #define FSMOUNT_CLOEXEC 0x00000001
> +#define FSMOUNT_NAMESPACE 0x00000002 /* Create the mount in a new mount namespace */
The commit message states: "This would be used to beautify mount syscall
arguments". Will this header sync be enough to beautify the new flag?
Looking at tools/perf/builtin-trace.c, the fsmount_flags array is manually
hardcoded:
static const char *fsmount_flags[] = {
[1] = "CLOEXEC",
};
Since [2] = "NAMESPACE" is not present in this array, ARRAY_SIZE(fsmount_flags)
remains 2. The loop in strarray__scnprintf_flags() checks up to index 1.
Does the FSMOUNT_NAMESPACE flag also need to be manually added to the
fsmount_flags array in builtin-trace.c for the beautification to work?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260503193137.27465-1-namhyung@kernel.org?part=3
next prev parent reply other threads:[~2026-05-04 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 19:31 [PATCH 0/5] perf build: Update kernel headers Namhyung Kim
2026-05-03 19:31 ` [PATCH 1/5] perf trace: Sync linux/socket.h with the kernel source Namhyung Kim
2026-05-03 19:31 ` [PATCH 2/5] perf trace: Sync uapi/linux/fs.h " Namhyung Kim
2026-05-03 19:31 ` [PATCH 3/5] perf trace: Sync uapi/linux/mount.h " Namhyung Kim
2026-05-04 19:33 ` sashiko-bot [this message]
2026-05-03 19:31 ` [PATCH 4/5] perf trace: Sync uapi/linux/sched.h " Namhyung Kim
2026-05-04 19:33 ` sashiko-bot
2026-05-03 19:31 ` [PATCH 5/5] perf build: Add make check-headers target Namhyung Kim
2026-05-04 19:33 ` sashiko-bot
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=20260504193332.01FC6C2BCB8@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=sashiko@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.