From: Sami Tolvanen <samitolvanen@google.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Petr Pavlu <petr.pavlu@suse.com>,
Daniel Gomez <da.gomez@samsung.com>,
linux-modules@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org,
Sami Tolvanen <samitolvanen@google.com>
Subject: [PATCH v3 0/5] gendwarfksyms: Add more kABI rules
Date: Wed, 7 May 2025 23:14:04 +0000 [thread overview]
Message-ID: <20250507231403.377725-7-samitolvanen@google.com> (raw)
Hi,
While looking deeper into the genksyms hacks that have been
needed during Android's 5.10 and 5.15 GKI lifecycles so far,
we found a few instances that are not covered by the existing
gendwarfksyms kABI stability rules. The first case involved
appending new members to a partially opaque data structure, and
the second case completely changing opaque types due to a large
backport that was necessary for both stability and security.
These patches add rules that allow distribution maintainers
to deal with structure size changes, and as a last resort, to
completely override a type string used for version calculation.
Sami
---
v3:
- Added a patch to drop documentation section numbers based
on Masahiro's suggestion.
v2: https://lore.kernel.org/r/20250505212401.3379699-6-samitolvanen@google.com/
- Cleaned up type string parsing based on Petr's feedback.
v1: https://lore.kernel.org/r/20250430214049.2658716-6-samitolvanen@google.com/
---
Sami Tolvanen (5):
gendwarfksyms: Clean up kABI rule look-ups
gendwarfksyms: Add a kABI rule to override byte_size attributes
gendwarfksyms: Add a kABI rule to override type strings
Documentation/kbuild: Drop section numbers
Documentation/kbuild: Add new gendwarfksyms kABI rules
Documentation/kbuild/gendwarfksyms.rst | 141 +++++++++++++++++-----
scripts/gendwarfksyms/dwarf.c | 14 ++-
scripts/gendwarfksyms/examples/kabi.h | 21 +++-
scripts/gendwarfksyms/examples/kabi_ex.c | 7 ++
scripts/gendwarfksyms/examples/kabi_ex.h | 101 +++++++++++++++-
scripts/gendwarfksyms/gendwarfksyms.h | 2 +
scripts/gendwarfksyms/kabi.c | 143 ++++++++++++++---------
scripts/gendwarfksyms/types.c | 140 +++++++++++++++++++---
8 files changed, 470 insertions(+), 99 deletions(-)
base-commit: 92a09c47464d040866cf2b4cd052bc60555185fb
--
2.49.0.987.g0cc8ee98dc-goog
next reply other threads:[~2025-05-07 23:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 23:14 Sami Tolvanen [this message]
2025-05-07 23:14 ` [PATCH v3 1/5] gendwarfksyms: Clean up kABI rule look-ups Sami Tolvanen
2025-05-07 23:14 ` [PATCH v3 2/5] gendwarfksyms: Add a kABI rule to override byte_size attributes Sami Tolvanen
2025-05-07 23:14 ` [PATCH v3 3/5] gendwarfksyms: Add a kABI rule to override type strings Sami Tolvanen
2025-05-07 23:14 ` [PATCH v3 4/5] Documentation/kbuild: Drop section numbers Sami Tolvanen
2025-05-07 23:14 ` [PATCH v3 5/5] Documentation/kbuild: Add new gendwarfksyms kABI rules Sami Tolvanen
2025-05-08 23:42 ` [PATCH v3 0/5] gendwarfksyms: Add more " Masahiro Yamada
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=20250507231403.377725-7-samitolvanen@google.com \
--to=samitolvanen@google.com \
--cc=da.gomez@samsung.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mcgrof@kernel.org \
--cc=petr.pavlu@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox