From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/20514] New: Write a kabidiff utility to compare the ABI of Linux Kernel trees
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <bug-20514-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=20514
Bug ID: 20514
Summary: Write a kabidiff utility to compare the ABI of Linux
Kernel trees
Product: libabigail
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: dodji at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
It would be useful to have an ABI comparison tool, just like abidiff, that
would compare the ABI exposed by the Linux kernel to its modules.
As an initial step, I guess we can consider functions (and global variables)
that are considered part of the kernel's internal ABI to be those marked by the
macros EXPORT_SYMBOL and EXPORT_SYMBOL_GPL.
The tool would consider a kernel "tree" to be the union of the kernel binary
and the accompanying modules that are intended to be loaded by it.
As a first step, though, just considering the kernel binary would be a good
proof of concept of what we can come up with.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-08-25 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 dodji at redhat dot com [this message]
2016-01-01 0:00 ` [Bug default/20514] Write a command line tool " dodji at redhat dot com
2016-01-01 0:00 ` [Bug default/20514] Write a kabidiff utility " dodji at redhat dot com
2016-01-01 0:00 ` [Bug default/20514] Write a command line tool " dodji at redhat dot com
2016-01-01 0:00 ` [Bug default/20514] Write a kabidiff utility " dodji at redhat dot com
2017-01-01 0:00 ` [Bug default/20514] Write a command line tool " dodji at redhat dot com
2017-01-01 0:00 ` dodji at redhat dot com
2017-01-01 0:00 ` dodji at redhat dot com
2017-01-01 0:00 ` dodji at redhat dot com
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=bug-20514-9487@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).