From: Jiri Pirko <jiri@resnulli.us>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
eric.dumazet@gmail.com, hannes@stressinduktion.org,
jdmason@kudzu.us, yoshfuji@linux-ipv6.org, kuznet@ms2.inr.ac.ru,
jmorris@namei.org, kaber@trash.net, herbert@gondor.apana.org.au
Subject: Re: [patch net REPOST 2/3] ip6_output: do skb ufo init for peeked non ufo skb as well
Date: Sat, 19 Oct 2013 08:23:00 +0200 [thread overview]
Message-ID: <20131019062300.GA1500@minipsycho.orion> (raw)
In-Reply-To: <5261819B.8020801@cogentembedded.com>
Fri, Oct 18, 2013 at 08:44:43PM CEST, sergei.shtylyov@cogentembedded.com wrote:
>Hello.
>
>On 10/18/2013 09:13 PM, Jiri Pirko wrote:
>
>>Now, if user application does:
>>sendto len<mtu flag MSG_MORE
>>sendto len>mtu flag 0
>>The skb is not treated as fragmented one because it is not initialized
>>that way. So move the initialization to fix this.
>
>>introduced by:
>>commit e89e9cf539a28df7d0eb1d0a545368e9920b34ac "[IPv4/IPv6]: UFO Scatter-gather approach"
>
>>Signed-off-by: Jiri Pirko <jiri@resnulli.us>
>>---
>> net/ipv6/ip6_output.c | 26 ++++++++++++++------------
>> 1 file changed, 14 insertions(+), 12 deletions(-)
>
>>diff --git a/net/ipv6/ip6_output.c b/net/ipv6/ip6_output.c
>>index a54c45c..c6cfa2f 100644
>>--- a/net/ipv6/ip6_output.c
>>+++ b/net/ipv6/ip6_output.c
>[...]
>>@@ -1036,20 +1035,23 @@ static inline int ip6_ufo_append_data(struct sock *sk,
>> skb->transport_header = skb->network_header + fragheaderlen;
>>
>> skb->protocol = htons(ETH_P_IPV6);
>>- skb->ip_summed = CHECKSUM_PARTIAL;
>> skb->csum = 0;
>>
>>- /* Specify the length of each IPv6 datagram fragment.
>>- * It has to be a multiple of 8.
>>- */
>>- skb_shinfo(skb)->gso_size = (mtu - fragheaderlen -
>>- sizeof(struct frag_hdr)) & ~7;
>>- skb_shinfo(skb)->gso_type = SKB_GSO_UDP;
>>- ipv6_select_ident(&fhdr, rt);
>>- skb_shinfo(skb)->ip6_frag_id = fhdr.identification;
>> __skb_queue_tail(&sk->sk_write_queue, skb);
>>- }
>>+ } else if (skb_is_gso(skb))
>>+ goto append;
>
> According to Documentation/CodingStyle, there should be {} in both
>arms of *if* statement if there's {} in one of them.
Yep, you are right. I wonder why scripts/checkpatch.pl do not warn about
this. I will send v2. Thanks
>
>WBR, Sergei
>
next prev parent reply other threads:[~2013-10-19 6:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 17:13 [patch net REPOST 0/3] UFO fixes Jiri Pirko
2013-10-18 17:13 ` [patch net REPOST 1/3] udp6: respect IPV6_DONTFRAG sockopt in case there are pending frames Jiri Pirko
2013-10-18 17:13 ` [patch net REPOST 2/3] ip6_output: do skb ufo init for peeked non ufo skb as well Jiri Pirko
2013-10-18 18:44 ` Sergei Shtylyov
2013-10-19 6:23 ` Jiri Pirko [this message]
2013-10-18 17:13 ` [patch net REPOST 3/3] ip_output: " Jiri Pirko
2013-10-18 18:45 ` Sergei Shtylyov
2013-10-18 17:15 ` [patch net REPOST 0/3] UFO fixes Jiri Pirko
2013-10-18 17:20 ` Hannes Frederic Sowa
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=20131019062300.GA1500@minipsycho.orion \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=herbert@gondor.apana.org.au \
--cc=jdmason@kudzu.us \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=yoshfuji@linux-ipv6.org \
/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).