From: Florian Westphal <fw@strlen.de>
To: David Miller <davem@davemloft.net>
Cc: fw@strlen.de, netdev@vger.kernel.org, hannes@stressinduktion.org,
Maxime Bizon <mbizon@freebox.fr>
Subject: Re: [PATCH -next, V3 0/2] net: force refragmentation for DF reassembed skbs
Date: Fri, 22 May 2015 21:26:51 +0200 [thread overview]
Message-ID: <20150522192651.GA3629@breakpoint.cc> (raw)
In-Reply-To: <20150522.150310.2248217318352290500.davem@davemloft.net>
David Miller <davem@davemloft.net> wrote:
[ cc'd Maxime Bizon ]
> From: Florian Westphal <fw@strlen.de>
> Date: Fri, 22 May 2015 16:32:49 +0200
>
> > IP (ttl 64, id 12345, offset 0, flags [+, DF], proto UDP (17), length 1204)
> > 192.168.7.1.42 > 10.23.42.2.42: UDP, length 1400
> > IP (ttl 64, id 12345, offset 1184, flags [DF], proto UDP (17), length 244)
> > 192.168.7.1 > 10.23.42.2: ip-proto-17
>
> I almost consider a fragment with DF set an oxymoron.
>
> How does this happen?
Good question. I have no idea why or how this happens.
But it does happen, see e.g. following bug report:
http://marc.info/?l=linux-netdev&m=139870308431986&w=2
Maxime, do you recall what type of traffic generates
the DF-fragments you reported?
Thanks.
next prev parent reply other threads:[~2015-05-22 19:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 14:32 [PATCH -next, V3 0/2] net: force refragmentation for DF reassembed skbs Florian Westphal
2015-05-22 14:32 ` [PATCH -next 1/2] net: ipv4: avoid repeated calls to ip_skb_dst_mtu helper Florian Westphal
2015-05-22 14:43 ` Hannes Frederic Sowa
2015-05-22 14:32 ` [PATCH -next 2/2] ip_fragment: don't forward defragmented DF packet Florian Westphal
2015-05-22 14:45 ` Hannes Frederic Sowa
2015-05-22 19:03 ` [PATCH -next, V3 0/2] net: force refragmentation for DF reassembed skbs David Miller
2015-05-22 19:26 ` Florian Westphal [this message]
2015-05-26 9:57 ` Maxime Bizon
2015-05-26 14:50 ` Florian Westphal
2015-05-22 22:52 ` Hannes Frederic Sowa
2015-05-27 17:04 ` 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=20150522192651.GA3629@breakpoint.cc \
--to=fw@strlen.de \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=mbizon@freebox.fr \
--cc=netdev@vger.kernel.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).