Re: [PATCH] selftests: nft_queue: conntrack expiration requeue

[Florian Westphal <fw@strlen.de>]

Antonio Ojea <aojea@google.com> wrote:
> > So I went with 'no rules that adds one, no need for ct label
> > extension space allocation'.
> 
> But that does not consider the people that just use netlink to set the
> labels ... from a 1k altitude , can you do a check on the first
> update/create/delete label to initialize the extension?

Yes, but in that case it is not possible to disable it again.

Rule based on/off means we can disable it once the rule is gone.

I'd propose to extend the label allocation to when a 'ct lablel'
rule is added rather than just 'ct label set'.

> Another question related, is it required for the label value to be
> always 16 bytes?

As far as I can see ctnetlink enforces the len must be a multiple of 4
and at most 16 bytes.