From: Jason Wang <jasowang@redhat.com>
To: Vlad Yasevich <vyasevic@redhat.com>, netdev@vger.kernel.org
Cc: daniel.lezcano@free.fr, nightnord@gmail.com, kaber@trash.net,
eric.dumazet@gmail.com, mst@redhat.com
Subject: Re: [PATCH v2 net 1/2] mactap: Fix checksum errors for non-gso packets in bridge mode
Date: Wed, 30 Apr 2014 10:46:40 +0800 [thread overview]
Message-ID: <53606410.7080105@redhat.com> (raw)
In-Reply-To: <1398780591-10644-2-git-send-email-vyasevic@redhat.com>
On 04/29/2014 10:09 PM, Vlad Yasevich wrote:
> The following is a problematic configuration:
>
> VM1: virtio-net device connected to macvtap0@eth0
> VM2: e1000 device connect to macvtap1@eth0
>
> The problem is is that virtio-net supports checksum offloading
> and thus sends the packets to the host with CHECKSUM_PARTIAL set.
> On the other hand, e1000 does not support any acceleration.
>
> For small TCP packets (and this includes the 3-way handshake),
> e1000 ends up receiving packets that only have a partial checksum
> set. This causes TCP to fail checksum validation and to drop
> packets. As a result tcp connections can not be established.
>
> Commit 3e4f8b787370978733ca6cae452720a4f0c296b8
> macvtap: Perform GSO on forwarding path.
> fixes this issue for large packets wthat will end up undergoing GSO.
> This commit adds a check for the non-GSO case and attempts to
> compute the checksum for partially checksummed packets in the
> non-GSO case.
>
> CC: Daniel Lezcano <daniel.lezcano@free.fr>
> CC: Patrick McHardy <kaber@trash.net>
> CC: Andrian Nord <nightnord@gmail.com>
> CC: Eric Dumazet <eric.dumazet@gmail.com>
> CC: Michael S. Tsirkin <mst@redhat.com>
> CC: Jason Wang <jasowang@redhat.com>
> Signed-off-by: Vlad Yasevich <vyasevic@redhat.com>
> ---
> drivers/net/macvtap.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/net/macvtap.c b/drivers/net/macvtap.c
> index ff111a8..3381c4f 100644
> --- a/drivers/net/macvtap.c
> +++ b/drivers/net/macvtap.c
> @@ -322,6 +322,15 @@ static rx_handler_result_t macvtap_handle_frame(struct sk_buff **pskb)
> segs = nskb;
> }
> } else {
> + /* If we receive a partial checksum and the tap side
> + * doesn't support checksum offload, compute the checksum.
> + * Note: it doesn't matter which checksum feature to
> + * check, we either support them all or none.
> + */
> + if (skb->ip_summed == CHECKSUM_PARTIAL &&
> + !(features & NETIF_F_ALL_CSUM) &&
> + skb_checksum_help(skb))
> + goto drop;
> skb_queue_tail(&q->sk.sk_receive_queue, skb);
> }
>
Acked-by: Jason Wang <jasowang@redhat.com>
next prev parent reply other threads:[~2014-04-30 2:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 14:09 [PATCH v2 net 0/2] Fix macvtap checksum errors in bridge mode Vlad Yasevich
2014-04-29 14:09 ` [PATCH v2 net 1/2] mactap: Fix checksum errors for non-gso packets " Vlad Yasevich
2014-04-29 13:21 ` Michael S. Tsirkin
2014-04-30 2:46 ` Jason Wang [this message]
2014-04-29 14:09 ` [PATCH v2 net 2/2] Revert "macvlan : fix checksums error when we are in bridge mode" Vlad Yasevich
2014-04-29 13:22 ` Michael S. Tsirkin
2014-04-30 2:47 ` Jason Wang
2014-04-30 20:15 ` [PATCH v2 net 0/2] Fix macvtap checksum errors in bridge mode David Miller
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=53606410.7080105@redhat.com \
--to=jasowang@redhat.com \
--cc=daniel.lezcano@free.fr \
--cc=eric.dumazet@gmail.com \
--cc=kaber@trash.net \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nightnord@gmail.com \
--cc=vyasevic@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.