From: Christian Franke <Christian.Franke@t-online.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] framework for building modules externally
Date: Wed, 05 Nov 2008 07:57:38 +0100 [thread overview]
Message-ID: <491143E2.4040705@t-online.de> (raw)
In-Reply-To: <20081104193911.GA26419@thorin>
Robert Millan wrote:
>> ...
>> How do you treat differences in ABI ?
>>
>> Dis-allow loading of module with different value of ABI ? Or were you
>> planning that module itself adapts to different versions of GRUB 2 ABI's?
>>
>
> The module itself could:
>
> GRUB_MOD_INIT(foo)
> {
> if (grub_abi != GRUB_ABI)
> {
> grub_printf ("abi mismatch!\n");
> return;
> }
>
> /* register our commands/terminals/disks/whatever */
> }
>
>
Alternative: Export a symbol describing the ABI version in kernel
("grub_abi_3_14"). Access this symbol in each module (this can be hidden
in GRUB_MOD_INIT).
Then loading a module with wrong ABI version fails due to undefined symbol.
--
Christian Franke
next prev parent reply other threads:[~2008-11-05 6:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 12:32 [PATCH] framework for building modules externally Robert Millan
2008-11-01 19:02 ` Robert Millan
2008-11-04 18:55 ` Vesa Jääskeläinen
2008-11-04 19:07 ` Robert Millan
2008-11-04 19:13 ` Vesa Jääskeläinen
2008-11-04 19:39 ` Robert Millan
2008-11-05 6:57 ` Christian Franke [this message]
2008-11-05 9:42 ` Robert Millan
2008-11-05 21:41 ` Christian Franke
2008-11-06 14:52 ` __FILE__ (Re: [PATCH] framework for building modules externally) Robert Millan
2008-11-06 21:10 ` Christian Franke
2008-11-07 19:02 ` Robert Millan
2008-11-10 20:39 ` Christian Franke
2008-11-06 14:54 ` [PATCH] framework for building modules externally Robert Millan
2008-11-06 20:43 ` Christian Franke
2008-11-07 19:05 ` Robert Millan
2008-11-08 11:33 ` Robert Millan
2008-11-10 20:44 ` Christian Franke
2009-04-10 23:19 ` phcoder
2009-04-13 13:55 ` Robert Millan
2008-11-05 9:51 ` Robert Millan
2008-11-08 11:29 ` Robert Millan
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=491143E2.4040705@t-online.de \
--to=christian.franke@t-online.de \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.