From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,surenb@google.com,sj@kernel.org,hao.ge@linux.dev,arnd@arndb.de,akpm@linux-foundation.org
Subject: [merged mm-hotfixes-stable] alloc_tag-avoid-implicit-padding-in-uapi.patch removed from -mm tree
Date: Sat, 26 Sep 2026 13:55:39 -0700 [thread overview]
Message-ID: <20260926205539.990731F000FF@smtp.kernel.org> (raw)
The quilt patch titled
Subject: alloc_tag: avoid implicit padding in uapi
has been removed from the -mm tree. Its filename was
alloc_tag-avoid-implicit-padding-in-uapi.patch
This patch was dropped because it was merged into the mm-hotfixes-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Arnd Bergmann <arnd@arndb.de>
Subject: alloc_tag: avoid implicit padding in uapi
Date: Tue, 15 Sep 2026 22:23:47 +0200
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>
---
include/uapi/linux/alloc_tag.h | 1 +
1 file changed, 1 insertion(+)
--- a/include/uapi/linux/alloc_tag.h~alloc_tag-avoid-implicit-padding-in-uapi
+++ a/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 {
_
Patches currently in -mm which might be from arnd@arndb.de are
mm-vmscan-avoid-false-positive-wuninitialized-warning-again.patch
reply other threads:[~2026-09-26 20:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260926205539.990731F000FF@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=hao.ge@linux.dev \
--cc=mm-commits@vger.kernel.org \
--cc=sj@kernel.org \
--cc=surenb@google.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 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.