Netdev List
 help / color / mirror / Atom feed
From: Tom Herbert <tom@quantonium.net>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, hannes@stressinduktion.org,
	alex.popov@linux.com, Tom Herbert <tom@quantonium.net>
Subject: [PATCH v2 net-next 0/2] flow_dissector: Flow dissector fixes
Date: Fri,  1 Sep 2017 14:04:10 -0700	[thread overview]
Message-ID: <20170901210412.2915-1-tom@quantonium.net> (raw)

This patch set fixes some basic issues with __skb_flow_dissect function.

Items addressed:
  - Cleanup control flow in the function; in particular eliminate a
    bunch of goto's and implement a simplified control flow model
  - Add limits for number of encapsulations and headers that can be
    dissected

v2:
  - Simplify the logic for limits on flow dissection. Just set the
    limit based on the number of headers the flow dissector can
    processes. The accounted headers includes encapsulation headers,
    extension headers, or other shim headers.

Tested:

Ran normal traffic, GUE, and VXLAN traffic.

*** BLURB HERE ***

Tom Herbert (2):
  flow_dissector: Cleanup control flow
  flow_dissector: Add limit for number of headers to dissect

 include/net/flow_dissector.h |   8 ++
 net/core/flow_dissector.c    | 242 +++++++++++++++++++++++++++++--------------
 2 files changed, 172 insertions(+), 78 deletions(-)

-- 
2.11.0

             reply	other threads:[~2017-09-01 21:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-01 21:04 Tom Herbert [this message]
2017-09-01 21:04 ` [PATCH v2 net-next 1/2] flow_dissector: Cleanup control flow Tom Herbert
2017-09-01 21:04 ` [PATCH v2 net-next 2/2] flow_dissector: Add limit for number of headers to dissect Tom Herbert
2017-09-05 18:45 ` [PATCH v2 net-next 0/2] flow_dissector: Flow dissector fixes David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170901210412.2915-1-tom@quantonium.net \
    --to=tom@quantonium.net \
    --cc=alex.popov@linux.com \
    --cc=davem@davemloft.net \
    --cc=hannes@stressinduktion.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox