flow_dissector: Fix fragment handling for header length computation
authorAlexander Duyck <aduyck@mirantis.com>
Wed, 24 Feb 2016 17:29:44 +0000 (09:29 -0800)
committerDavid S. Miller <davem@davemloft.net>
Wed, 24 Feb 2016 18:58:04 +0000 (13:58 -0500)
commit43d2ccb3c122a47524019d1831a54f07f7fcb978
treec0d4dbf3cf5f6576fcc25199d922eb23ae193169
parent918c023f29ab2dd8c63cfcc6a1239ee15933871a
flow_dissector: Fix fragment handling for header length computation

It turns out that for IPv4 we were reporting the ip_proto of the fragment,
and for IPv6 we were not.  This patch updates that behavior so that we
always report the IP protocol of the fragment.  In addition it takes the
steps of updating the payload offset code so that we will determine the
start of the payload not including the L4 header for any fragment after the
first.

Signed-off-by: Alexander Duyck <aduyck@mirantis.com>
Acked-by: Tom Herbert <tom@herbertland.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/core/flow_dissector.c