summaryrefslogtreecommitdiff
path: root/include/uapi/linux
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2026-09-15 22:23:47 +0200
committerAndrew Morton <akpm@linux-foundation.org>2026-09-26 13:55:10 -0700
commit347c6ed8cf7768883252e106994de62c7947f0a0 (patch)
tree8d01534e2b927685b767c9b74e74111c15ee6b9e /include/uapi/linux
parent72c3d682c165b836b54a3d07a01f72e39c47022c (diff)
downloadlinux-347c6ed8cf7768883252e106994de62c7947f0a0.tar.gz
linux-347c6ed8cf7768883252e106994de62c7947f0a0.zip
alloc_tag: avoid implicit padding in uapi
The implied padding causes a harmless warning when testing the uapi headers with -Wpadded that could in theory indicate incompatibilities or data leaks: ./usr/include/linux/alloc_tag.h:41:1: error: padding struct size to alignment boundary with 7 bytes [-Werror=padded] The code here is fine, but it's better to make the padding explicit and avoid the warning here. Link: https://lore.kernel.org/20260916065830.1619425-1-arnd@kernel.org Link: https://lore.kernel.org/20260915202404.3568029-1-arnd@kernel.org Fixes: 1d581ab2348c ("alloc_tag: add ioctl to /proc/allocinfo") Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Acked-by: Suren Baghdasaryan <surenb@google.com> Acked-by: SJ Park <sj@kernel.org> Acked-by: Hao Ge <hao.ge@linux.dev>
Diffstat (limited to 'include/uapi/linux')
-rw-r--r--include/uapi/linux/alloc_tag.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/uapi/linux/alloc_tag.h b/include/uapi/linux/alloc_tag.h
index e3ad94444864..7d4618bea043 100644
--- a/include/uapi/linux/alloc_tag.h
+++ b/include/uapi/linux/alloc_tag.h
@@ -38,6 +38,7 @@ struct allocinfo_counter {
__u64 bytes;
__u64 calls;
__u8 accurate;
+ __u8 pad[7];
} __attribute__((aligned(8)));
struct allocinfo_tag_data {