From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gao feng Subject: Re: [PATCH] route:ip_rt_frag_needed always return unzero Date: Wed, 19 Oct 2011 16:07:46 +0800 Message-ID: <4E9E8552.1050405@cn.fujitsu.com> References: <1318921469-25599-1-git-send-email-gaofeng@cn.fujitsu.com> <1318929797.2657.21.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> <4E9E2929.7070701@cn.fujitsu.com> <1318996187.19139.8.camel@edumazet-laptop> <4E9E5E1C.5020603@cn.fujitsu.com> <20111019072628.GS1830@secunet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Eric Dumazet , davem@davemloft.net, kuznet@ms2.inr.ac.ru, jmorris@namei.org, netdev@vger.kernel.org To: Steffen Klassert Return-path: Received: from cn.fujitsu.com ([222.73.24.84]:57530 "EHLO song.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1751425Ab1JSIHU (ORCPT ); Wed, 19 Oct 2011 04:07:20 -0400 In-Reply-To: <20111019072628.GS1830@secunet.com> Sender: netdev-owner@vger.kernel.org List-ID: 2011.10.19 15:26, Steffen Klassert wrote: > > On udp and raw sockets, the user is responsible to adjust the packet > size according to the mtu value he may find in the socket's error queue. > So we shoud provide the user with this information, even in the unlikely > case where we could not create an inet_peer. > Agree.Maybe we should modify mtu immediately when create inet_peer failed > > It is valid in the sense that we should not provide the user > with a mtu information if we know that the value we got from > the icmp packet ist bogus. But perhaps we can think about > making the check for a valid mtu unconditionally and let > ip_rt_frag_needed return a valid mtu in any case. > > I think we should return the pmtu in icmp packet to the raw socket, and the valid mtu to tcp_v4_err or something else. thanks Steffen.