netdev - Re: [patch v1 00/12] IPVS: SIP Persistence Engine

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:	Fri, 17 Sep 2010 11:52:32 +0900
From:	Simon Horman <horms@...ge.net.au>
To:	Patrick McHardy <kaber@...sh.net>
Cc:	lvs-devel@...r.kernel.org, netdev@...r.kernel.org,
	netfilter@...r.kernel.org, netfilter-devel@...r.kernel.org,
	Jan Engelhardt <jengelh@...ozas.de>,
	Stephen Hemminger <shemminger@...tta.com>,
	Wensong Zhang <wensong@...ux-vs.org>,
	Julian Anastasov <ja@....bg>
Subject: Re: [patch v1 00/12] IPVS: SIP Persistence Engine

On Thu, Sep 16, 2010 at 10:12:07AM +0200, Patrick McHardy wrote:
> Am 22.08.2010 14:44, schrieb Simon Horman:
> > This patch series adds load-balancing of UDP SIP based on Call-ID to
> > IPVS as well as a frame-work for extending IPVS to handle alternate
> > persistence requirements.
> > 
> > REVISIONS
> > 
> > This is "patch v1" of this series, which addresses a few minor problems, as
> > annotated on a per-patch basis, since the initial "rfc" posting. Internally
> > there were 4 rfc versions, 0.1, 0.2, 0.3 and 0.4, some of the notes for
> > some of the patches reflect those versions.
> 
> This looks fine to me as far as I can judge.
> 
> > CODE AVAILABILITY
> > 
> > The kernel patches (13) are available in git as the pe-0.4 branch of
> > git://git.kernel.org/pub/scm/linux/kernel/git/horms/lvs-test-2.6.git
> 
> Just to clarify, do you want me to merge this version?

Assuming that it applies cleanly, yes.
Otherwise I can re-base an re-post.

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