netdev - Re: [GIT PULL nf-next-2.6] IPVS changes for 2.6.38-rc3

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:	Wed, 26 Jan 2011 09:57:47 +1000
From:	Simon Horman <horms@...ge.net.au>
To:	Patrick McHardy <kaber@...sh.net>
Cc:	lvs-devel@...r.kernel.org, netfilter-devel@...r.kernel.org,
	netdev@...r.kernel.org, Changli Gao <xiaosuo@...il.com>,
	Julian Anastasov <ja@....bg>
Subject: Re: [GIT PULL nf-next-2.6] IPVS changes for 2.6.38-rc3

On Tue, Jan 25, 2011 at 03:01:35PM +0100, Patrick McHardy wrote:
> On 25.01.2011 14:17, Simon Horman wrote:
> > Hi Patrick,
> > 
> > please consider pulling
> >   git://git.kernel.org/pub/scm/linux/kernel/git/horms/lvs-test-2.6.git for-patrick
> > 
> > Which includes the following changes, both of which I believe 2.6.38 material.
> > 
> > Changli Gao (1):
> >       netfilter: ipvs: fix compiler warnings
> > 
> > Hans Schillstrom (1):
> >       IPVS netns BUG, register sysctl for root ns
> 
> That tree is based on nf-next-2.6, so I can't pull this into my nf-2.6
> tree.

Hi Patrick,

Sorry about this.

As it turns out I was mistaken in assuming that the IPVS netns changes
had been merged into nf-2.6. They haven't, they only exist in net-next-2.6.

All of the recent patches that I have passed on to you relate to the IPVS
netns changes so nf-next-2.6 is the right place for these fixes. So could
you please pull the above tree into nf-next-2.6? I do not believe there are
any nf-2.6 changes at this time.

Thanks

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