From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: pshelar@nicira.com, netdev@vger.kernel.org, jesse@nicira.com
Subject: Re: [PATCH net-next] net: fix possible wrong checksum generation
Date: Mon, 28 Jan 2013 00:28:01 -0500 (EST) [thread overview]
Message-ID: <20130128.002801.200824996474874108.davem@davemloft.net> (raw)
In-Reply-To: <1359182077.5222.132.camel@edumazet-glaptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 25 Jan 2013 22:34:37 -0800
> From: Eric Dumazet <edumazet@google.com>
>
> Pravin Shelar mentioned that GSO could potentially generate
> wrong TX checksum if skb has fragments that are overwritten
> by the user between the checksum computation and transmit.
>
> He suggested to linearize skbs but this extra copy can be
> avoided for normal tcp skbs cooked by tcp_sendmsg().
>
> This patch introduces a new SKB_GSO_SHARED_FRAG flag, set
> in skb_shinfo(skb)->gso_type if at least one frag can be
> modified by the user.
>
> Typical sources of such possible overwrites are {vm}splice(),
> sendfile(), and macvtap/tun/virtio_net drivers.
>
> Tested:
...
> Performance of the SENDFILE is impacted by the extra allocation and
> copy, and because we use order-0 pages, while the TCP_STREAM uses
> bigger pages.
>
> Reported-by: Pravin Shelar <pshelar@nicira.com>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
Applied, thanks Eric.
next prev parent reply other threads:[~2013-01-28 5:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 22:16 [PATCH 2/2] v2 GRE: Add segmentation offload for GRE Pravin B Shelar
2013-01-24 23:29 ` Eric Dumazet
2013-01-25 0:14 ` Pravin Shelar
2013-01-25 1:34 ` Eric Dumazet
2013-01-25 3:38 ` Pravin Shelar
2013-01-25 19:52 ` Eric Dumazet
2013-01-26 6:34 ` [PATCH net-next] net: fix possible wrong checksum generation Eric Dumazet
2013-01-28 5:28 ` David Miller [this message]
2013-01-28 18:35 ` Ben Hutchings
2013-01-29 19:30 ` Pravin Shelar
2013-01-25 1:14 ` [PATCH 2/2] v2 GRE: Add segmentation offload for GRE Michał Mirosław
2013-01-28 18:28 ` Ben Hutchings
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=20130128.002801.200824996474874108.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.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).