[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130927105856.GF28287@order.stressinduktion.org>
Date: Fri, 27 Sep 2013 12:58:56 +0200
From: Hannes Frederic Sowa <hannes@...essinduktion.org>
To: Oussama Ghorbel <oghorbell@...il.com>
Cc: "David S. Miller" <davem@...emloft.net>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
James Morris <jmorris@...ei.org>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Patrick McHardy <kaber@...sh.net>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] IPv6: Allow the MTU of ipip6 tunnel to be set below 1280
On Fri, Sep 27, 2013 at 11:45:48AM +0100, Oussama Ghorbel wrote:
> The ip6_tunnel.c module would be then dependent on ip_tunnel.c and may
> be it would not be good thing?
It could just be a static inline in some shared header. So there would
be no compile-time dependency.
> As I have check in v3.10 there is no call from ip6_tunnel to ip_tunnel...
>
> For information, there is no check for the maximum MTU for ipv4 in the
> patch as this is not done for ipv6.
I understand, but it would be better to limit the MTU here. There is a
(non-jumo) IPV6_MAXPLEN constant.
Looking through the source it seems grev6 does actually check this,
so it would not hurt adding them here, too.
Otherwise, I think your patch is fine.
Greetings,
Hannes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists