[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20070320.093949.117333367.yoshfuji@linux-ipv6.org>
Date: Tue, 20 Mar 2007 09:39:49 +0100 (CET)
From: YOSHIFUJI Hideaki / 吉藤英明
<yoshfuji@...ux-ipv6.org>
To: pekkas@...core.fi
Cc: davem@...emloft.net, kaber@...sh.net, netdev@...r.kernel.org,
yoshfuji@...ux-ipv6.org
Subject: Re: 2.6.20.3-rc1 / iproute2 hoplimit 2^32-1 vs 2^8-1
In article <Pine.LNX.4.64.0703201026300.25136@...core.fi> (at Tue, 20 Mar 2007 10:27:51 +0200 (EET)), Pekka Savola <pekkas@...core.fi> says:
> On Mon, 19 Mar 2007, David Miller wrote:
> > From: Patrick McHardy <kaber@...sh.net>
> > Date: Mon, 19 Mar 2007 16:27:29 +0100
> >
> >> Mhh actually this looks intentional:
> >>
> >> icmpv6_send and some other output functions do:
> >> int hlimit;
> >> ...
> >> if (hlimit < 0)
> >> hlimit = dst_metric(dst, RTAX_HOPLIMIT);
> >> if (hlimit < 0)
> >> hlimit = ipv6_get_hoplimit(dst->dev);
> >
> > Yep, negative value has a specific meaning.
>
> Which seems to indicate that the kernel-internal implementation has a
> need to store a negative TTL. Reporting it to the userspace as a
> negative doesn't seem right though?
I think it is better to fix iproute2 instead, 1) to treat the variable as
int, or, 2) not to show such variable.
--yoshfuji
-
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
Powered by blists - more mailing lists