As written in the commit message: Depending on your conntrackd configuration, events might get lost, leaving stuck entries in the cache forever. Skip checking the conntrack ID to allow for lazy cleanup by when a new entry that is represented by the same tuple is added. Signed-off-by: Nick Hainke <vincent@systemli.org> |
||
---|---|---|
.. | ||
001-endianness_fix.patch | ||
002-conntrackd-do-not-include-conntrack-ID-in-hashtable-cmp.patch |