From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: GRO/GSO hiding PMTU?
Date: Thu, 10 Feb 2011 15:07:59 -0800 (PST) [thread overview]
Message-ID: <20110210.150759.59671055.davem@davemloft.net> (raw)
In-Reply-To: <20110210.145555.39165146.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Thu, 10 Feb 2011 14:55:55 -0800 (PST)
> I suspect that the packet arrives on eth1, accumulates into GRO, and
> thus marked as GSO as well, then GSO/TSO on output to eth0 is
> re-segmenting things transparently, and we're not getting the ICMP
> frag-needed message and the packet drop because of the skb_is_gso()
> check in ip_forward().
>
> if (unlikely(skb->len > dst_mtu(&rt->dst) && !skb_is_gso(skb) &&
> (ip_hdr(skb)->frag_off & htons(IP_DF))) && !skb->local_df) {
> IP_INC_STATS(dev_net(rt->dst.dev), IPSTATS_MIB_FRAGFAILS);
> icmp_send(skb, ICMP_DEST_UNREACH, ICMP_FRAG_NEEDED,
> htonl(dst_mtu(&rt->dst)));
> goto drop;
> }
>
> So if that's what is happening, that's cute, but I think we need to
> fix this :-)
>
> Perhaps the check in ip_forward() should instead validate the gso_size
> in the skb_is_gso() case?
>
> That'd be a little tricky since gso_size is an MSS value whereas what
> we're checking against (skb->len) is the full packet size, headers and
> all.
Nevermind, I turned off gso/tso on eth0 (outgoing interface) and it still
happens.
I guess netfilter or something else is causing this.
next prev parent reply other threads:[~2011-02-10 23:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 22:55 GRO/GSO hiding PMTU? David Miller
2011-02-10 23:07 ` David Miller [this message]
2011-02-11 0:07 ` Herbert Xu
2011-02-10 23:50 ` Herbert Xu
2011-02-11 6:22 ` David Miller
2011-02-11 6:35 ` David Miller
2011-02-11 6:41 ` Herbert Xu
2011-02-11 7:06 ` David Miller
2011-02-11 6:37 ` Herbert Xu
2011-02-11 7:07 ` 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=20110210.150759.59671055.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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).