Re: [nf_tables] pipapo: inserting an interval that strictly contains an existing one is accepted; rbtree rejects the same insert

Understood - thanks for the detailed explanations.

Best regards,


On Tue, Aug 11, 2026 at 7:32 PM Florian Westphal <[email protected]> wrote:
>
> Wei Fang <[email protected]> wrote:
> > The report is about inserting a *new interval that strictly
> > contains an existing one*.  On a pipapo set: first insert
> > [1.1.1.1..1.1.1.11), then insert [1.1.1.0..1.1.1.12).
> > On the kernel under test:
>
> There is currently no way to detect this is in an efficient
> manner.
>
> Kernel would have to lookup all combinations of
> 1.1.1.0..1.1.1.12: 1.1.1.1, 1.1.1.2, 1.1.1.3, ...
>
> It checks start and end key only.