From: Tom Herbert <tom@quantonium.net>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, alex.popov@linux.com,
hannes@stressinduktion.org, Tom Herbert <tom@quantonium.net>
Subject: [PATCH net-next 0/2] flow_dissector: Flow dissector fixes
Date: Thu, 31 Aug 2017 15:22:37 -0700 [thread overview]
Message-ID: <20170831222239.21509-1-tom@quantonium.net> (raw)
This patch set fixes some basic issues with __skb_flow_dissect function.
Items addressed:
- Cleanup control flow in the fucntion; in particular eliminate a
bunch of goto's and implement a simplified control flow model
- Add limits for number of encapsulations of extension headers that
can be dissected
Tested:
Ran normal traffic, GUE, and VXLAN traffic.
Tom Herbert (2):
flow_dissector: Cleanup control flow
flow_dissector: Add limits for encapsulation and EH
include/net/flow_dissector.h | 9 ++
net/core/flow_dissector.c | 267 ++++++++++++++++++++++++++++++-------------
2 files changed, 198 insertions(+), 78 deletions(-)
--
2.11.0
next reply other threads:[~2017-08-31 22:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 22:22 Tom Herbert [this message]
2017-08-31 22:22 ` [PATCH net-next 1/2] flow_dissector: Cleanup control flow Tom Herbert
2017-09-01 12:26 ` Simon Horman
2017-09-01 12:35 ` Hannes Frederic Sowa
2017-09-01 16:12 ` Tom Herbert
2017-08-31 22:22 ` [PATCH net-next 2/2] flow_dissector: Add limits for encapsulation and EH Tom Herbert
2017-09-01 12:22 ` Simon Horman
2017-09-01 13:32 ` Hannes Frederic Sowa
2017-09-01 15:38 ` Tom Herbert
2017-09-01 16:35 ` Hannes Frederic Sowa
2017-09-01 16:49 ` Tom Herbert
2017-09-01 17:05 ` Hannes Frederic Sowa
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=20170831222239.21509-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