Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ABI testing as part of the CI #54

Open
evelikov opened this issue Jul 17, 2024 · 0 comments
Open

Add ABI testing as part of the CI #54

evelikov opened this issue Jul 17, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@evelikov
Copy link
Collaborator

evelikov commented Jul 17, 2024

We don't want to cause ABI breakages and manually tracking this is error prone.

Recently I've noticed a few miss placed symbols in the version script [1]. Seemingly those got flagged up in the Debian packaging [2] [3], although the maintainer didn't report that to the kmod team.

Looking through the ABI-laboratory [4], there is one more ABI break.

(Fixes for those will follow shortly, doing some auditing atm Sent: https://lore.kernel.org/linux-modules/[email protected]/T/#t)

Fedora/RH [5] already uses abi-lab/libabigail and they have some handy blog posts [5][6]. Some of the Gnome projects also make use of libabigail.

[1] https://lore.kernel.org/linux-modules/[email protected]/T/#t
[2] https://salsa.debian.org/md/kmod/-/commit/e5c3f7cc04ac523a66ad8a2cd8cbc04b51d55391
[3] https://salsa.debian.org/md/kmod/-/commit/c7c9dd68adba0aeac53b9402ca1f278d43c62988
[4] https://abi-laboratory.pro/index.php?view=timeline&l=kmod
[5] https://developers.redhat.com/blog/2020/04/02/how-to-write-an-abi-compliance-checker-using-libabigail
[6] https://developers.redhat.com/articles/2022/01/06/whats-new-libabigail-20#

@lucasdemarchi lucasdemarchi added the enhancement New feature or request label Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants