netdev - Re: [PATCH 00/26] IPVS: Add first IPv6 support to IPVS.

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 for Android: free password hash cracker in your pocket

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

Message-ID: <f4845fc0806111253l4f1fea4fyef05cdc41ca45911@mail.gmail.com>
Date:	Wed, 11 Jun 2008 21:53:39 +0200
From:	"Julius Volz" <juliusv@...gle.com>
To:	"Patrick McHardy" <kaber@...sh.net>
Cc:	lvs-devel@...r.kernel.org, netdev@...r.kernel.org,
	"Vince Busam" <vbusam@...gle.com>
Subject: Re: [PATCH 00/26] IPVS: Add first IPv6 support to IPVS.

On Wed, Jun 11, 2008 at 9:31 PM, Patrick McHardy <kaber@...sh.net> wrote:
> Julius Volz wrote:
>> It is clearly laid out to be able to be changed over time, hence the
>> ipvsadm version check...
>
> The usual way is to add new members at the end. The history shows no
> changes at all to these structs though.

Not in git history at least. No version number change there either
(maybe the LVS folks know more about the history).

Adding members at the end sounds interesting! The current structs have
the v4 address members in the middle of the struct, so you couldn't
use a union of v4 and v6 anymore, but since it's only in the userspace
interface, that shouldn't matter much. If this allows us to keep the
interface backwards compatible in an easy way, that would be great.

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