On Thu, Nov 21, 2019 at 11:41:24AM +0100, Phil Sutter wrote:
> The commit this fixes accidentally broke a rather exotic use-case which
> is but used in set-simple.t of tests/monitor:
>
> | # nft 'add element t s { 22-25 }; delete element t s { 22-25 }'
>
> Since ranges are now checked for existence in userspace before delete
> command is submitted to kernel, the second command above was rejected
> because the range in question wasn't present in cache yet. Fix this by
> adding new interval set elements to cache after creating the batch job
> for them.
Applied, with minor glitch:
if (set->init != NULL &&
set->flags & NFT_SET_INTERVAL)
Just in case the set definition is empty.
Thanks Phil.
