netdev - Re: question: update_pmtu doesn't update dst mtu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140403115809.GA13354@order.stressinduktion.org>
Date:	Thu, 3 Apr 2014 13:58:09 +0200
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	"Ilya V. Matveychikov" <i.matveychikov@...uritycode.ru>
Cc:	netdev@...r.kernel.org
Subject: Re: question: update_pmtu doesn't update dst mtu

On Thu, Apr 03, 2014 at 03:37:33PM +0400, Ilya V. Matveychikov wrote:
> Hello,
> 
> Is this a place where I can post questions not the patches? If so, can anybody
> explain me what the problem I have when trying to update dst PMTU value.
> 
> So, the scheme is the following:
> 
>                   skb->dst                   rt(pmtu)
> IN_DEV (MTU 1500) -------> TUNNEL (MTU 1440) -------> OUT_DEV (MTU 1500)
> 
> I have a simple tunnel_xmit function that handles all the packets that goes
> trough the tunnel. So, I have an skb with valid skb->dst value (filled earlier
> in ip_input_route_noref).
> 
> Next, when encapsulation is done, I needed to get an output route for the packet
> (rt at the scheme). At this point I know that the output route may have a PMTU
> value that is different from the OUT_DEV->mtu. So, I'm trying to update the
> input skb->dst route's PMTU with the update_pmtu function. It seems that all is
> OK, but when I trying to get the dst mtu value (using dst_mtu(skb_dst(skb))) I
> always get the value of 1440 (TUNNEL's MTU):
> 
> tunnel_xmit:
>     ...
>     pmtu = dst_mtu(&rt->dst) - OVERHEAD; // pmtu = 1300, for example
>     skb_dst(skb)->ops->update_pmtu(skb_dst(skb), NULL, skb, pmtu);
>     // dst_mtu(skb_dst(skb)) still returns 1440
> 
> Looking through the code gives me that rt_pmtu is always 0 for the skb->dst
> entry and ipv4_mtu that called via the dst->ops->mtu() uses dev->mtu :(

At this point you have to drop skb_dst and have to relookup the route. During
that a new dst will be created which gets the mtu value from the next hop
exception, which got created by update_pmtu.

Normally routes are checked with dst_check if they are still valid
and a relookup should happen. In your example just do the relookup
unconditionally.

Greetings,

  Hannes

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html