From: David Miller <davem@davemloft.net>
To: simon.horman@netronome.com
Cc: pshelar@nicira.com, netdev@vger.kernel.org, dev@openvswitch.org
Subject: Re: [PATCH v2] openvswitch: retain parsed IPv6 header fields in flow on error skipping extension headers
Date: Sat, 29 Aug 2015 13:40:19 -0700 (PDT) [thread overview]
Message-ID: <20150829.134019.1423323256685869514.davem@davemloft.net> (raw)
In-Reply-To: <1440806541-22729-1-git-send-email-simon.horman@netronome.com>
From: Simon Horman <simon.horman@netronome.com>
Date: Sat, 29 Aug 2015 09:02:21 +0900
> When an error occurs skipping IPv6 extension headers retain the already
> parsed IP protocol and IPv6 addresses in the flow. Also assume that the
> packet is not a fragment in the absence of information to the contrary;
> that is always use the frag_off value set by ipv6_skip_exthdr().
>
> This allows matching on the IP protocol and IPv6 addresses of packets
> with malformed extension headers.
>
> Signed-off-by: Simon Horman <simon.horman@netronome.com>
Applied to net-next, thanks Simon.
prev parent reply other threads:[~2015-08-29 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 0:02 [PATCH v2] openvswitch: retain parsed IPv6 header fields in flow on error skipping extension headers Simon Horman
2015-08-29 20:40 ` 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=20150829.134019.1423323256685869514.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
--cc=simon.horman@netronome.com \
/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;
as well as URLs for NNTP newsgroup(s).