From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: David Miller <davem@davemloft.net>
Cc: yanghy@cn.fujitsu.com, yoshfuji@linux-ipv6.org, netdev@vger.kernel.org
Subject: Re: [PATCH] IPv6:fix the return interface index when get it while no message is received
Date: Fri, 08 Aug 2008 10:58:04 -0400 [thread overview]
Message-ID: <489C5EFC.6030006@hp.com> (raw)
In-Reply-To: <20080807.230334.239030482.davem@davemloft.net>
David Miller wrote:
> From: Yang Hongyang <yanghy@cn.fujitsu.com>
> Date: Fri, 08 Aug 2008 13:59:54 +0800
>
>> Yang Hongyang wrote:
>>> when I use getsockopt(sk, IPPROTO_IPV6, IPV6_2292PKTOPTIONS,(char *)incmsg, &cnt)
>>> to get receiving interface index while no message is received,
>>>
>>> What interface index should be returned?
>> When get receiving interface index while no message is received,
>> the bounded device's index of the socket should be returned?
>>
>> Signed-off-by: Yang Hongyang<yanghy@cn.fujitsu.com>
>
> To me it seems to be an undefined operation.
>
> One cannot expect something valid from this socket option until a
> packet really is received on the socket.
Here is what 2292 has to say:
> The corresponding receive option
>
> getsockopt(fd, IPPROTO_IPV6, IPV6_PKTOPTIONS, &buf, &len);
>
> returns a buffer with one or more ancillary data objects for all the
> optional receive information that the application has previously
> specified that it wants to receive. The fourth argument points to
> the buffer that is filled in by the call. The fifth argument is a
> pointer to a value-result integer: when the function is called the
> integer specifies the size of the buffer pointed to by the fourth
> argument, and on return this integer contains the actual number of
> bytes that were returned. The application processes this buffer
> exactly as if the buffer were returned by recvmsg() as control
> information.
So, there return value should be any sticky options set.
In the case of PKTINFO, the interface should be either 0 or the one
set by the sticky option.
The address should be should be from the options or IN6ADDR_ANY.
This is all for RFC2292 style.
For RFC 3542 style, there what should be done:
Issuing getsockopt() for the above options will return the sticky
option value i.e., the value set with setsockopt(). If no sticky
option value has been set getsockopt() will return the following
values:
- For the IPV6_PKTINFO option, it will return an in6_pktinfo
structure with ipi6_addr being in6addr_any and ipi6_ifindex being
zero.
-vlad
next prev parent reply other threads:[~2008-08-08 14:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 4:27 get receiving interface index while no message is received Yang Hongyang
2008-08-08 5:59 ` [PATCH] IPv6:fix the return interface index when get it " Yang Hongyang
2008-08-08 6:03 ` David Miller
2008-08-08 14:58 ` Vlad Yasevich [this message]
2008-08-18 5:41 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2008-08-18 6:07 Yang Hongyang
2008-08-18 6:22 ` David Miller
2008-08-18 13:31 ` Vlad Yasevich
2008-08-19 5:38 ` David Miller
2008-08-19 6:28 ` Yang Hongyang
2008-08-19 13:36 ` Vlad Yasevich
2008-08-20 2:56 ` Yang Hongyang
2008-08-20 13:10 ` Vlad Yasevich
2008-08-22 11:54 ` David Miller
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=489C5EFC.6030006@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=yanghy@cn.fujitsu.com \
--cc=yoshfuji@linux-ipv6.org \
/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).