public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "maennich at android dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/28954] add Linux Kernel symbol namespace support
Date: Fri, 11 Mar 2022 12:20:44 +0000	[thread overview]
Message-ID: <bug-28954-9487-ATMz5Jksoe@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28954-9487@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28954

Matthias Maennich <maennich at android dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |maennich at android dot com

--- Comment #4 from Matthias Maennich <maennich at android dot com> ---
The namespaces are not part of the linkage name as that would confuse linkers,
loaders and external tools (and would also break some).

Instead the namespace is embedded in the ksymtab along with a MODVERSION CRC.
The ksymtab is basically an array of structs (struct kernel_symbol) that is
referred to from the symtab by the __ksymtab__<symbol> entries.

At module load time, every required symbol of a module is looked up in the list
of existing symbols (largely coming from vmlinux, and possibly from another
module) and loading is denied if the symbol has an attached namespace AND the
module does not declare the namespace as imported. (similarly loading is denied
upon a mismatch of the CRCs). 

Hence, the ABI breakage happens if the exported symbol newly has a namespace
attached while the consuming module does not (yet) declare the import of said
namespace.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2022-03-11 12:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 13:25 [Bug default/28954] New: " gprocida at google dot com
2022-03-10 15:52 ` Ben Woodard
2022-03-10 15:53 ` [Bug default/28954] " woodard at redhat dot com
2022-03-10 16:25 ` gprocida at google dot com
2022-03-10 17:25 ` gprocida at google dot com
2022-03-11 12:20 ` maennich at android dot com [this message]

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-28954-9487-ATMz5Jksoe@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).