From: Brian Haley <brian.haley@hp.com>
To: David Miller <davem@davemloft.net>
Cc: rdenis@simphalempin.com, akpm@osdl.org, netdev@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 7665] New: getsockopt(IPV6_*CAST_HOPS) returns -1
Date: Wed, 13 Dec 2006 12:28:47 -0500 [thread overview]
Message-ID: <4580384F.4070904@hp.com> (raw)
In-Reply-To: <20061212.171121.21596915.davem@davemloft.net>
David Miller wrote:
> I wonder, since the most accurate return value is tied to the route,
> what is expected of this getsockopt() before a socket's identity
> (and therefore route) is known?
A search for RTAX_HOPLIMIT found very little code that ever sets it,
iproute2 was the only important one, so the interface/system default is
probably the only one that's ever used.
-Brian
prev parent reply other threads:[~2006-12-13 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-11 17:56 Fw: [Bugme-new] [Bug 7665] New: getsockopt(IPV6_*CAST_HOPS) returns -1 Andrew Morton
2006-12-11 21:55 ` Brian Haley
2006-12-12 8:08 ` Rémi Denis-Courmont
2006-12-12 21:16 ` Brian Haley
2006-12-12 22:38 ` Rémi Denis-Courmont
2006-12-13 1:11 ` David Miller
2006-12-13 17:28 ` Brian Haley [this message]
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=4580384F.4070904@hp.com \
--to=brian.haley@hp.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rdenis@simphalempin.com \
/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).