[Bug 1451] nft add element fails when preceded by nft get element or nft delete element commands

bugzilla-daemon at netfilter.org bugzilla-daemon at netfilter.org
Sat Aug 29 12:29:27 CEST 2020


https://bugzilla.netfilter.org/show_bug.cgi?id=1451

Pablo Neira Ayuso <pablo at netfilter.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #15 from Pablo Neira Ayuso <pablo at netfilter.org> ---
(In reply to kfm from comment #11)
> After creating a set similar to yours and adding a "delete element" command,
> it blew up on the 11th iteration. As luck would have it, one of my other
> hosts had already been rebooted with the patch that Pablo mentioned applied,
> so I tested there and found that the patch appears to resolve the issue.
> 
> For the record, I'm still running 5.7.17, only with the addition of the
> following patches.
> 
> netfilter-nft_set_rbtree-handle-outcomes-of-tree-rotations-in-overlap-
> detection.patch
> netfilter-nft_set_rbtree_detect-partial-overlap-with-start-endpoint-match.
> patch
> netfilter-nf_tables-fix-destination-register-zeroing.patch

Thanks for confirming these patches fix the issue.

Closing this ticket.

-- 
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.netfilter.org/pipermail/netfilter-buglog/attachments/20200829/5dccde84/attachment.html>


More information about the netfilter-buglog mailing list