From: Jiri Pirko <jiri@resnulli.us>
To: netdev@vger.kernel.org
Cc: yoshfuji@linux-ipv6.org, davem@davemloft.net,
kuznet@ms2.inr.ac.ru, jmorris@namei.org, kaber@trash.net,
herbert@gondor.apana.org.au, eric.dumazet@gmail.com,
hannes@stressinduktion.org
Subject: Re: [PATCH] ipv6: udp packets following an UFO enqueued packet need also be handled by UFO
Date: Wed, 2 Oct 2013 13:20:52 +0200 [thread overview]
Message-ID: <20131002112052.GC1528@minipsycho.brq.redhat.com> (raw)
In-Reply-To: <20131001232534.GM10771@order.stressinduktion.org>
Wed, Oct 02, 2013 at 01:25:34AM CEST, hannes@stressinduktion.org wrote:
>On Tue, Oct 01, 2013 at 11:47:21PM +0200, Hannes Frederic Sowa wrote:
>> The strange thing is that if I don't do the IPV6_MTU setsockopt I don't
>> get an oops.
>
>This is incorrect, it just depends on the size of the writes and on the
>interface mtu.
>
>> IPv4 seems to work without problems, too.
>
>I also get kernel oopses from IPv4 now, too.
This patch should fix this on ipv4 as well:
Subject: ip_output: do skb ufo init for peeked non ufo skb as well
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.
Signed-off-by: Jiri Pirko <jiri@resnulli.us>
---
net/ipv4/ip_output.c | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/net/ipv4/ip_output.c b/net/ipv4/ip_output.c
index a04d872..bd21c5d 100644
--- a/net/ipv4/ip_output.c
+++ b/net/ipv4/ip_output.c
@@ -772,15 +772,19 @@ static inline int ip_ufo_append_data(struct sock *sk,
/* initialize protocol header pointer */
skb->transport_header = skb->network_header + fragheaderlen;
- skb->ip_summed = CHECKSUM_PARTIAL;
skb->csum = 0;
- /* specify the length of each IP datagram fragment */
- skb_shinfo(skb)->gso_size = maxfraglen - fragheaderlen;
- skb_shinfo(skb)->gso_type = SKB_GSO_UDP;
+
__skb_queue_tail(queue, skb);
- }
+ } else if (skb_is_gso(skb))
+ goto append;
+
+ skb->ip_summed = CHECKSUM_PARTIAL;
+ /* specify the length of each IP datagram fragment */
+ skb_shinfo(skb)->gso_size = maxfraglen - fragheaderlen;
+ skb_shinfo(skb)->gso_type = SKB_GSO_UDP;
+append:
return skb_append_datato_frags(sk, skb, getfrag, from,
(length - transhdrlen));
}
--
1.8.3.1
next prev parent reply other threads:[~2013-10-02 11:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-21 4:27 [PATCH] ipv6: udp packets following an UFO enqueued packet need also be handled by UFO Hannes Frederic Sowa
2013-09-23 0:43 ` Hannes Frederic Sowa
2013-09-24 15:43 ` David Miller
2013-09-30 11:43 ` Jiri Pirko
2013-09-30 17:23 ` Hannes Frederic Sowa
2013-10-01 10:58 ` Jiri Pirko
2013-10-01 12:09 ` Hannes Frederic Sowa
2013-10-01 12:32 ` Hannes Frederic Sowa
2013-10-01 21:47 ` Hannes Frederic Sowa
2013-10-01 23:25 ` Hannes Frederic Sowa
2013-10-02 8:58 ` Jiri Pirko
2013-10-02 10:41 ` Eric Dumazet
2013-10-02 12:12 ` Hannes Frederic Sowa
2013-10-02 13:03 ` Hannes Frederic Sowa
2013-10-02 15:14 ` Eric Dumazet
2013-10-02 16:27 ` Neterion and UFO handling [was: Re: [PATCH] ipv6: udp packets following an UFO enqueued packet need also be handled by UFO] Hannes Frederic Sowa
2013-10-07 16:53 ` Hannes Frederic Sowa
2013-10-07 17:19 ` Jon Mason
2013-10-07 17:27 ` Hannes Frederic Sowa
2013-10-08 8:07 ` Jon Mason
2013-10-08 13:00 ` Eric Dumazet
2013-10-08 14:53 ` Hannes Frederic Sowa
2013-10-17 4:45 ` Hannes Frederic Sowa
2013-10-18 7:52 ` Jiri Pirko
2013-10-23 16:35 ` Jon Mason
2013-10-23 18:15 ` Hannes Frederic Sowa
2013-10-02 10:33 ` [PATCH] ipv6: udp packets following an UFO enqueued packet need also be handled by UFO Jiri Pirko
2013-10-02 12:01 ` Hannes Frederic Sowa
2013-10-02 11:20 ` Jiri Pirko [this message]
2013-10-02 11:53 ` Eric Dumazet
2013-10-02 12:10 ` Jiri Pirko
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=20131002112052.GC1528@minipsycho.brq.redhat.com \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=herbert@gondor.apana.org.au \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--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).