Nicholas Piggin <npig...@gmail.com> a écrit:
> On Thu, 1 Dec 2016 11:48:09 +0100
> Stanislav Kozina <skoz...@redhat.com> wrote:
>> On 12/01/2016 05:13 AM, Don Zickus wrote:
>> > I think GregKH pointed to one such tool, libabigail? We are working on
>> > others too.
>> I should mention one of the others here:
> Now this seems much better for distro ABI checking.
Right, Incidentally, Fedora does distro-wide ABI verfication for
userspace libraries updates in a given stable distribution. You can
look at an example of output of the libabigail-based tool that compares
a new version of an ELF library to it's latest stable version:
The results of those ABI comparison can browsed at
Of course, you can run the comparison yourself by using a
libabigail-based tool like
https://sourceware.org/libabigail/manual/abipkgdiff.html which takes
.deb and .rpm packages.
We are currently working on making libabigail-based tools understand
Linux kernel specifities so that we can run that kind of analysis on
Kernel updates too. Ideally, when this is done, you should be able to
just use abipkgdiff on two Linux Kernel packages and get the same kind
> The next question is, do they need any kernel support for rare cases
> where they do have to break the ABI of an export? Simple rename of the
> function with a _v2 postfix might be enough. We could retain some per
> symbol versioning in the kernel if needed, but how much would it
> actually help?
As a reviewer of the ABI change report emitted by the tool, if what you
want is to say "I reviewed that ABI change and it's OK, so please do not
show it to me next time", then you can feed the tool with a "suppression
specification". It's a text file in the INI syntax in which you can
specify the kind of change you want the tool to suppress from its
So I don't think you need to do anything to the source code of the
Kernel in the cases where you need to change the ABI. Just tell the
tool about that change.