Skip to content

Commit

Permalink
docs: XDP DoS considerations for Troubleshooting and Monitoring
Browse files Browse the repository at this point in the history
Signed-off-by: Jesper Dangaard Brouer <brouer@redhat.com>
  • Loading branch information
netoptimizer committed Sep 20, 2016
1 parent 3925249 commit a4e60e2
Showing 1 changed file with 8 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -93,3 +93,11 @@ Two options are on the table currently:
Another option is adding tracepoint to these situations. It is much
more flexible than counters. The downside is that these error
events might never be caught, if the tracepoint isn't active.

An important design consideration is the monitor facility must not be
too expensive to execute, even-though events like :ref:`XDP_ABORTED`
and :ref:`action fall-through` should be very rare events. This is
because an external attacker (given the DDoS uses-cases) might find a
way to trigger these events, which would then serve as an attack
vector against XDP.

0 comments on commit a4e60e2

Please sign in to comment.