public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: 結友 <miagetegorann@gmail.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-kernel v3 1/2] d/scripts: correctly compare namespaced ABI exports
Date: Fri, 23 Oct 2026 22:20:14 -0700	[thread overview]
Message-ID: <CAEP6gkZR0vOaurMKnNPfXtLrDP+oA-F=LNSmwosoSKZr97B5cw@mail.gmail.com> (raw)
In-Reply-To: <CAEP6gkYf4izZpzBU8Arg9XJRXY83TLK8kna23CL8ttVqpdjiZA@mail.gmail.com>

abi-generate emits a different field order for namespaced exports. Parse
both layouts explicitly so the module name does not become part of the
symbol name. Otherwise, building hv_vmbus into vmlinux falsely reports
three existing namespaced exports as missing.

Compare the actual export type and namespace, preserving hash and missing
symbol checks and symbol/module blacklists. Reject added or changed
namespace requirements, malformed entries and duplicate symbols. Fix the
export-type diagnostic's printf argument separator.

Add 12 ABI regression tests, including end-to-end abi-generate output,
relocation, hash changes, GPL restrictions, namespaces and skip handling.
Document the check and test command, and ignore Python bytecode caches.

All 12 tests pass under WSL2 Ubuntu 24.04. Rechecking the existing
7.0.14-26-pve build artifacts with SKIPABI=0 preserves all 32,726 symbols,
their CRCs and export types, with only the expected 47 VMBus relocations.

Signed-off-by: 結友 <miagetegorann@gmail.com>
---
 .gitignore                     |   1 +
 README                         |   8 ++
 debian/scripts/abi-check       |  56 ++++++++++---
 debian/tests/test_abi_check.py | 140 +++++++++++++++++++++++++++++++++
 4 files changed, 192 insertions(+), 13 deletions(-)
 create mode 100644 debian/tests/test_abi_check.py

  reply	other threads:[~2026-10-24  5:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-24  5:19 [PATCH pve-kernel v3 0/2] fix #8027: restore built-in Hyper-V VMBus 結友
2026-10-24  5:20 ` 結友 [this message]
2026-10-24  5:20 ` [PATCH pve-kernel v3 2/2] fix #8027: config: enable CONFIG_HYPERV_VMBUS 結友

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='CAEP6gkZR0vOaurMKnNPfXtLrDP+oA-F=LNSmwosoSKZr97B5cw@mail.gmail.com' \
    --to=miagetegorann@gmail.com \
    --cc=pve-devel@lists.proxmox.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal