Re: NFNL_NFA_NEST

[Patrick McHardy <kaber@trash.net>]

Pablo Neira Ayuso wrote:
> Patrick McHardy wrote:
>
>>>Yes, but we'll have to remove it sooner or later, so I understand this
>>>as a temporary solution, isn't it?
>>
>>
>>Not necessarily. The problem with the NEST bit is the receive
>>side of the kernel code, the generic stuff can't deal with it.
>>On the send-side we can simply manually OR it into the type value.
> 
> 
> I just started thinking that probably the generic infrastructure should
> support the nest bit. How crazy is this idea?


I don't know. It could accept them on the receive side without
further problems since probably no netlink user will define
more than 2^15 attributes, but could not send it since that
would break compatibility. Since the kernel doesn't need it
at all not sending it from userspace seems like a better
solution to me.