netdev - Re: [PATCH RFC 19/24] IPVS: Add IPv6 support flag to schedulers

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:	Thu, 21 Aug 2008 23:23:11 +1000
From:	Simon Horman <horms@...ge.net.au>
To:	Julius Volz <juliusv@...gle.com>
Cc:	netdev@...r.kernel.org, lvs-devel@...r.kernel.org, kaber@...sh.net,
	vbusam@...gle.com
Subject: Re: [PATCH RFC 19/24] IPVS: Add IPv6 support flag to schedulers

On Thu, Aug 21, 2008 at 12:21:39PM +0200, Julius Volz wrote:
> On Thu, Aug 21, 2008 at 3:48 AM, Simon Horman wrote:
> > On Wed, Aug 20, 2008 at 06:15:26PM +0200, Julius Volz wrote:
> >> Add 'supports_ipv6' flag to struct ip_vs_scheduler to indicate whether a
> >> scheduler supports IPv6. Set the flag to 1 in schedulers that work with
> >> IPv6, 0 otherwise. This flag is checked in a later patch while trying to
> >> add a service with a specific scheduler.
> >
> > I wonder if there are some spare bits inside the flags
> > member of ip_vs_scheduler that could be used for this purpose?
> 
> Hm, there isn't any 'flags' member or similar in that struct...
> 
> > Otherwise, I'm fine with this, we can juggle things around
> > later to use the other bits in supports_ipv6 for other things
> > if and when the need arises.
> 
> Yes, then we could also rename it to 'flags' once needed.
> 
> > Here is a version that applies against lvs-2.6
> 
> Thanks, I guess I should start basing all of my IPVS patches on this
> tree rather than net-2.6?

That would make things slightly more convenient for me.
But I'm not the only fish in the sea :-)

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