netdev - Re: IPVS network namespace aware ?

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:	Tue, 24 Aug 2010 10:53:58 +0200
From:	Hans Schillstrom <hans.schillstrom@...csson.com>
To:	Daniel Lezcano <daniel.lezcano@...e.fr>
CC:	lvs-devel@...r.kernel.org,
	"netfilter-devel@...r.kernel.org" <netfilter-devel@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: IPVS network namespace aware ?

Hi Daniel
The progress is good, so far I think everything is ported except for
Simon Hormans latest patch-set. 

Right now I'm struggling with NULL pointers :-)
i.e. seq_file doesn't carry any netns info.

In the example below *net will be invalid because seq->private is NULL.

static void *ip_vs_info_seq_next(struct seq_file *seq, ....) {
struct net *net = seq_file_net(seq);

single_open() seems to work, but seq_open() or seq_open_private().

As you can see I'm not ready, so help will be nice.
I'll remove some debugging stuff and send you a patch-set.

/Hans


On Mon, 2010-08-23 at 21:21 +0200, Daniel Lezcano wrote:
> On 08/06/2010 02:57 PM, Hans Schillstrom wrote:
> > Hello
> > Is there any one that have made ipvs network namespace aware ?
> > There is an urgent need of it within Ericsson.
> > I could not find any trace of it in any of the normal lists.
> >
> > I will start patching ipvs next week or give a helping hand to any
> > existing work.
> 
> Hi Hans,
> 
> do you have a patchset ready (or just a prototype) ? I will be glad to 
> help you ;)
> 
> Thanks
>    -- Daniel

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