Page MenuHomeFreeBSD

Flowtable cleaner problems (3 bugs).
ClosedPublic

Authored by rrs on Oct 27 2015, 11:50 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Oct 1, 7:37 AM
Unknown Object (File)
Sep 18 2024, 3:19 AM
Unknown Object (File)
Sep 8 2024, 10:52 PM
Unknown Object (File)
Sep 8 2024, 3:20 AM
Unknown Object (File)
Sep 7 2024, 5:56 PM
Unknown Object (File)
Sep 1 2024, 4:37 AM
Unknown Object (File)
Sep 1 2024, 4:37 AM
Unknown Object (File)
Sep 1 2024, 4:37 AM
Subscribers
None

Details

Summary

There are three bugs that I have found in flow-table

  1. The cleaner through an optimization that does not work will skip large parts of the hash tables leaving flow entries. This causes you to end up with a full table and basically in-effective use.
  2. There is a micro-optimization for IPv4 with the wrong comparison so it always falls to the non-optimized bcmp case.
  3. A routing table entry being not "UP" should cause the entry to be invalidated no matter what type of route it is (HOST or NET).
Test Plan

Running it in production at NF :-)

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

rrs retitled this revision from to Flowtable cleaner problems (3 bugs)..
rrs updated this object.
rrs edited the test plan for this revision. (Show Details)
rrs added reviewers: adrian, kmacy, imp, scottl.
adrian edited edge metadata.

monospaced text

This revision is now accepted and ready to land.Nov 2 2015, 8:45 PM
imp requested changes to this revision.Nov 2 2015, 9:02 PM
imp edited edge metadata.

You're lame style is making my eyes bleed.

flowtable.c
438

This is a style change.

This revision now requires changes to proceed.Nov 2 2015, 9:02 PM

I disagree with you imp

flowtable.c
438

Actually the style itself is fine.. what I did above matches other places (the routing
code for example) in how one checks for RTF_UP.

This revision was automatically updated to reflect the committed changes.