From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
To: netdev@vger.kernel.org, hannes@stressinduktion.org
Cc: Erik Hugne <erik.hugne@ericsson.com>,
YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Subject: Re: [PATCH RFC 1/2] ipv6: introdcue __ipv6_addr_needs_scope_id and ipv6_iface_scope_id helper functions
Date: Mon, 11 Feb 2013 22:36:35 +0900 [thread overview]
Message-ID: <5118F3E3.2080808@linux-ipv6.org> (raw)
In-Reply-To: <20130211111303.GA23991@order.stressinduktion.org>
Hannes Frederic Sowa wrote:
> This strictly a RFC only (I also left out my signed-off). This patch
> introduces helper functions to set and check for the need of scope ids.
>
> Suggested-by: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
> Cc: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
> ---
> include/net/ipv6.h | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/include/net/ipv6.h b/include/net/ipv6.h
> index 851d541..1f61dc9 100644
> --- a/include/net/ipv6.h
> +++ b/include/net/ipv6.h
> @@ -319,6 +319,19 @@ static inline int ipv6_addr_src_scope(const struct in6_addr *addr)
> return __ipv6_addr_src_scope(__ipv6_addr_type(addr));
> }
>
> +static inline bool __ipv6_addr_needs_scope_id(int type)
> +{
> + return type != IPV6_ADDR_ANY &&
> + !(type & IPV6_ADDR_LOOPBACK && type & IPV6_ADDR_UNICAST) &&
> + __ipv6_addr_src_scope(type) <= IPV6_ADDR_SCOPE_LINKLOCAL;
> +}
> +
> +static inline __u32 ipv6_iface_scope_id(const struct in6_addr *addr,
> + unsigned int iface)
> +{
> + return __ipv6_addr_needs_scope_id(__ipv6_addr_type(addr)) ? iface : 0;
> +}
> +
> static inline int ipv6_addr_cmp(const struct in6_addr *a1, const struct in6_addr *a2)
> {
> return memcmp(a1, a2, sizeof(struct in6_addr));
>
Yes, something like that.
--yoshfuji
next prev parent reply other threads:[~2013-02-11 13:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 8:49 [IPv6] interface-local multicast escapes the local node Erik Hugne
2013-02-06 12:12 ` Hannes Frederic Sowa
2013-02-06 13:07 ` Erik Hugne
2013-02-06 13:49 ` Hannes Frederic Sowa
2013-02-06 15:06 ` Erik Hugne
2013-02-06 15:12 ` Hannes Frederic Sowa
2013-02-06 15:32 ` YOSHIFUJI Hideaki
2013-02-06 16:04 ` Hannes Frederic Sowa
2013-02-06 16:18 ` Eric Dumazet
2013-02-06 16:25 ` Hannes Frederic Sowa
2013-02-06 16:49 ` YOSHIFUJI Hideaki
2013-02-07 1:00 ` Hannes Frederic Sowa
2013-02-07 7:28 ` Erik Hugne
2013-02-07 15:41 ` YOSHIFUJI Hideaki
2013-02-06 15:24 ` YOSHIFUJI Hideaki
2013-02-06 16:54 ` Hannes Frederic Sowa
2013-02-09 12:10 ` Hannes Frederic Sowa
2013-02-09 14:12 ` YOSHIFUJI Hideaki
2013-02-09 23:08 ` Hannes Frederic Sowa
2013-02-10 9:59 ` Hannes Frederic Sowa
2013-02-10 10:57 ` YOSHIFUJI Hideaki
2013-02-10 15:32 ` Hannes Frederic Sowa
2013-02-10 18:42 ` YOSHIFUJI Hideaki
2013-02-10 18:49 ` Hannes Frederic Sowa
2013-02-11 11:13 ` [PATCH RFC 1/2] ipv6: introdcue __ipv6_addr_needs_scope_id and ipv6_iface_scope_id helper functions Hannes Frederic Sowa
2013-02-11 13:36 ` YOSHIFUJI Hideaki [this message]
2013-02-11 11:13 ` [PATCH RFC 2/2] ipv6: use newly introduced helper functions __ipv6_addr_needs_scope_id and ipv6_iface_scope_id Hannes Frederic Sowa
2013-02-09 15:50 ` [IPv6] interface-local multicast escapes the local node YOSHIFUJI Hideaki
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=5118F3E3.2080808@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=erik.hugne@ericsson.com \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.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).