netdev - Re: [net-next] ipv6: Export in6addr

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 31 Aug 2010 16:01:35 -0700
From:	Ben Greear <greearb@...delatech.com>
To:	Ben Greear <greearb@...delatech.com>
CC:	netdev@...r.kernel.org
Subject: Re: [net-next] ipv6:  Export in6addr_any for use by modules.

On 08/31/2010 10:08 AM, Ben Greear wrote:
> Some upcoming cifs code, could make use of this, at least.

Actually, it's probably not worth the dependency on ipv6
for this small bit of code savings, so at least for cifs,
this probably isn't useful.

Thanks,
Ben

>
> Signed-off-by: Ben Greear<greearb@...delatech.com>
> ---
> :100644 100644 ab70a3f... 735989a... M	net/ipv6/addrconf.c
>   net/ipv6/addrconf.c |    1 +
>   1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c
> index ab70a3f..735989a 100644
> --- a/net/ipv6/addrconf.c
> +++ b/net/ipv6/addrconf.c
> @@ -230,6 +230,7 @@ static struct ipv6_devconf ipv6_devconf_dflt __read_mostly = {
>
>   /* IPv6 Wildcard Address and Loopback Address defined by RFC2553 */
>   const struct in6_addr in6addr_any = IN6ADDR_ANY_INIT;
> +EXPORT_SYMBOL(in6addr_any);
>   const struct in6_addr in6addr_loopback = IN6ADDR_LOOPBACK_INIT;
>   const struct in6_addr in6addr_linklocal_allnodes = IN6ADDR_LINKLOCAL_ALLNODES_INIT;
>   const struct in6_addr in6addr_linklocal_allrouters = IN6ADDR_LINKLOCAL_ALLROUTERS_INIT;


-- 
Ben Greear <greearb@...delatech.com>
Candela Technologies Inc  http://www.candelatech.com

--
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