From: Pravin Shelar <pshelar@ovn.org>
To: Ed Swierk <eswierk@skyportsystems.com>
Cc: ovs-dev <ovs-dev@openvswitch.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
Pravin Shelar <pshelar@nicira.com>,
Lance Richardson <lrichard@redhat.com>,
Benjamin Warren <ben@skyportsystems.com>,
Keith Holleman <holleman@skyportsystems.com>
Subject: Re: [PATCH] openvswitch: Trim off padding before L3 conntrack processing
Date: Wed, 13 Dec 2017 16:58:57 -0800 [thread overview]
Message-ID: <CAOrHB_CeoZ-MSmYNrMniccdTnT+VYUGEStq38CEi1HjtyGeJHA@mail.gmail.com> (raw)
In-Reply-To: <1513095439-128864-1-git-send-email-eswierk@skyportsystems.com>
On Tue, Dec 12, 2017 at 8:17 AM, Ed Swierk <eswierk@skyportsystems.com> wrote:
> A short IPv4 packet may have up to 6 bytes of padding following the IP
> payload when received on an Ethernet device.
>
> In the normal IPv4 receive path, ip_rcv() trims the packet to
> ip_hdr->tot_len before invoking NF_INET_PRE_ROUTING hooks (including
> conntrack). Then any subsequent L3+ processing steps, like
> nf_checksum(), use skb->len as the length of the packet, rather than
> referring back to ip_hdr->tot_len. In the IPv6 receive path, ip6_rcv()
> does the same using ipv6_hdr->payload_len.
>
> In the OVS conntrack receive path, this trimming does not occur, so
> the checksum verification in tcp_header() fails, printing "nf_ct_tcp:
> bad TCP checksum". Extra zero bytes don't affect the checksum, but the
> length in the IP pseudoheader does. That length is based on skb->len,
> and without trimming, it doesn't match the length the sender used when
> computing the checksum.
>
> With this change, OVS conntrack trims IPv4 and IPv6 packets prior to
> L3 processing.
>
> Signed-off-by: Ed Swierk <eswierk@skyportsystems.com>
> ---
> net/openvswitch/conntrack.c | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/net/openvswitch/conntrack.c b/net/openvswitch/conntrack.c
> index d558e882ca0c..3a7c9215c431 100644
> --- a/net/openvswitch/conntrack.c
> +++ b/net/openvswitch/conntrack.c
> @@ -1105,12 +1105,29 @@ int ovs_ct_execute(struct net *net, struct sk_buff *skb,
> const struct ovs_conntrack_info *info)
> {
> int nh_ofs;
> + unsigned int nh_len;
> int err;
>
> /* The conntrack module expects to be working at L3. */
> nh_ofs = skb_network_offset(skb);
> skb_pull_rcsum(skb, nh_ofs);
>
> + /* Trim to L3 length since nf_checksum() doesn't expect padding. */
Can you explore if nf_checksum can be changed to avoid the padding?
> + switch (skb->protocol) {
> + case htons(ETH_P_IP):
> + nh_len = ntohs(ip_hdr(skb)->tot_len);
> + break;
> + case htons(ETH_P_IPV6):
> + nh_len = ntohs(ipv6_hdr(skb)->payload_len)
> + + sizeof(struct ipv6hdr);
> + break;
> + default:
> + nh_len = skb->len;
> + }
> + err = pskb_trim_rcsum(skb, nh_len);
> + if (err)
> + return err;
> +
In case of error skb needs to be freed.
next prev parent reply other threads:[~2017-12-14 0:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 16:17 [PATCH] openvswitch: Trim off padding before L3 conntrack processing Ed Swierk
2017-12-14 0:58 ` Pravin Shelar [this message]
2017-12-14 20:05 ` Ed Swierk
2017-12-17 19:22 ` Pravin Shelar
2017-12-17 19:22 ` Pravin Shelar
2017-12-21 15:17 ` [PATCH v2] openvswitch: Trim off padding before L3+ netfilter processing Ed Swierk
2017-12-22 23:31 ` Pravin Shelar
2017-12-22 23:31 ` Pravin Shelar
2017-12-23 0:39 ` Ed Swierk
2017-12-23 0:39 ` Ed Swierk
2018-01-03 6:21 ` Pravin Shelar
2018-01-03 6:21 ` Pravin Shelar
2018-01-04 3:49 ` Ed Swierk
2018-01-05 3:36 ` Pravin Shelar
2018-01-05 3:36 ` Pravin Shelar
2018-01-05 18:14 ` Ed Swierk
2018-01-05 18:14 ` Ed Swierk
[not found] ` <CAO_EM_mQgURXZNtW7Qw7OkW4rjp4JWKBmqS8e4pUR=ZuiGCcZQ@mail.gmail.com>
2018-01-06 6:17 ` Pravin Shelar
2018-01-06 6:17 ` Pravin Shelar
[not found] ` <CAO_EM_=2qt3zSW1xprkLvcQVKGRTFMUQxCc4-cVLsUcRLj63Hg@mail.gmail.com>
2018-01-06 18:57 ` Pravin Shelar
2018-01-09 0:05 ` Pravin Shelar
2018-01-09 3:02 ` Ed Swierk
2018-01-09 22:06 ` Pravin Shelar
2018-01-09 3:02 ` Ed Swierk
2017-12-21 15:21 ` [PATCH v2 RESEND] " Ed Swierk
2017-12-21 15:21 ` Ed Swierk
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=CAOrHB_CeoZ-MSmYNrMniccdTnT+VYUGEStq38CEi1HjtyGeJHA@mail.gmail.com \
--to=pshelar@ovn.org \
--cc=ben@skyportsystems.com \
--cc=eswierk@skyportsystems.com \
--cc=holleman@skyportsystems.com \
--cc=lrichard@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=ovs-dev@openvswitch.org \
--cc=pshelar@nicira.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).