netdev - Re: [PATCH 02/26] IPVS: Change IPVS data structures to support IPv6 addresses.

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>] [day] [month] [year] [list]

Message-ID: <f4845fc0806111108q27a3d4f5o84ac638e58fb6ff0@mail.gmail.com>
Date:	Wed, 11 Jun 2008 20:08:38 +0200
From:	"Julius Volz" <juliusv@...gle.com>
To:	"Patrick McHardy" <kaber@...sh.net>
Cc:	lvs-devel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH 02/26] IPVS: Change IPVS data structures to support IPv6 addresses.

On Wed, Jun 11, 2008 at 7:52 PM, Patrick McHardy <kaber@...sh.net> wrote:
> Julius Volz wrote:
>>
>> On Wed, Jun 11, 2008 at 7:12 PM, Patrick McHardy <kaber@...sh.net> wrote:
>>
>>>
>>> include/net is always kernel only. At least it should be that way.
>>>
>>
>> ipvsadm has:
>>
>> INCLUDE         = -I/usr/src/linux/include -I.. -I.
>>
>> in its Makefile and then includes net/ip_vs.h. Even in the current version
>> :(
>>
>
> OK, thanks for the explanation.
>
>>>>  #define IP_VS_IFNAME_MAXLEN    16
>>>>  +union ip_vs_addr_user {
>>>> +       __be32                  v4;
>>>> +       struct in6_addr         v6;
>>>> +};
>>>>
>>>>
>>>
>>> Can't you use nf_inet_addr for this?
>>>
>>
>> Ah, yes. I either didn't know about this or wasn't sure if it was
>> appropriate to reuse that struct from netfilter. I will look into
>> putting this in!
>>
>>
>
> Thanks. But please remember to keep netdev CCed on responses
> to review.

Yes, sorry! Re-added the lists for this response.

Julius

-- 
Google Switzerland GmbH
--
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