From: Nikolay Aleksandrov
Date: Thu, 18 Feb 2016 21:51:26 +0100
> I just thought this version is a middle ground between the two solutions and
> still doesn't break user-space while being extensible.
Ok, I'll apply this series, thanks for taking me through your thought
process.
On 02/18/2016 09:37 PM, David Miller wrote:
> From: Nikolay Aleksandrov
> Date: Tue, 16 Feb 2016 12:46:52 +0100
>
>> Note that the reason we can't simply add an attribute after
>> MDBA_MDB_ENTRY_INFO is that current users (e.g. iproute2) walk over
>> the attribute list directly without checking f
From: Nikolay Aleksandrov
Date: Tue, 16 Feb 2016 12:46:52 +0100
> Note that the reason we can't simply add an attribute after
> MDBA_MDB_ENTRY_INFO is that current users (e.g. iproute2) walk over
> the attribute list directly without checking for the attribute type.
Honestly that sounds like a b
From: Nikolay Aleksandrov
Hi,
This small set allows to extend the per mdb entry exported attributes,
before this set we had only a structure exported which couldn't be changed
because we would've broken user-space, after this we extend the attribute
that was used for the structure and add per-mdb
