On Thu, Aug 15, 2024 at 05:39:20PM +0000, Sami Tolvanen wrote:
> Distributions that want to maintain a stable kABI need the ability to
> add reserved fields to kernel data structures that they anticipate
> will be modified during the ABI support timeframe, either by LTS
> updates or backports.
>
> With genksyms, developers would typically hide changes to the reserved
> fields from version calculation with #ifndef __GENKSYMS__, which would
> result in the symbol version not changing even though the actual type
> of the reserved field changes. When we process precompiled object
> files, this is again not an option.
>
> To support stable symbol versions for reserved fields, change the
> union type processing to recognize field name prefixes, and if the
> union contains a field name that starts with __kabi_reserved, only use
> the type of that field for computing symbol versions. In other words,
> let's assume we have a structure where we want to reserve space for
> future changes:
>
> struct struct1 {
> long a;
> long __kabi_reserved_0; /* reserved for future use */
> };
> struct struct1 exported;
>
> gendwarfksyms --debug produces the following output:
>
> variable structure_type struct1 {
> member base_type long int byte_size(8) encoding(5) data_member_location(0),
> member base_type long int byte_size(8) encoding(5) data_member_location(8),
> } byte_size(16);
> #SYMVER exported 0x67997f89
>
> To take the reserved field into use, a distribution would replace it
> with a union, with one of the fields keeping the __kabi_reserved name
> prefix for the original type:
>
> struct struct1 {
> long a;
> union {
> long __kabi_reserved_0;
> struct {
> int b;
> int v;
> };
> };
>
Ah, ignore my previous email, here's the --stable stuff.
But this all needs to go into some documentation somewhere, trying to
dig it out of a changelog is going to be impossible to point people at.
> +/* See dwarf.c:process_reserved */
> +#define RESERVED_PREFIX "__kabi_reserved"
Seems semi-sane, I can live with this.
I don't know if you want to take the next step and provide examples of
how to use this in "easy to use macros" for it all, but if so, that
might be nice. Especially as I have no idea how you are going to do
this with the rust side of things, this all will work for any structures
defined in .rs code, right?
thanks,
greg k-h
