Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: tom@quantonium.net
Cc: netdev@vger.kernel.org, hannes@stressinduktion.org, alex.popov@linux.com
Subject: Re: [PATCH v2 net-next 0/2] flow_dissector: Flow dissector fixes
Date: Tue, 05 Sep 2017 11:45:04 -0700 (PDT)	[thread overview]
Message-ID: <20170905.114504.207582830119826554.davem@davemloft.net> (raw)
In-Reply-To: <20170901210412.2915-1-tom@quantonium.net>

From: Tom Herbert <tom@quantonium.net>
Date: Fri,  1 Sep 2017 14:04:10 -0700

> 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.

Applied, thanks Tom.

      parent reply	other threads:[~2017-09-05 18:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-01 21:04 [PATCH v2 net-next 0/2] flow_dissector: Flow dissector fixes Tom Herbert
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 ` David Miller [this message]

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=20170905.114504.207582830119826554.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alex.popov@linux.com \
    --cc=hannes@stressinduktion.org \
    --cc=netdev@vger.kernel.org \
    --cc=tom@quantonium.net \
    /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