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] [day] [month] [year] [list]

Message-ID: <1282645495.25529.44.camel@seasc0214.dyn.rnd.as.sw.ericsson.se>
Date:	Tue, 24 Aug 2010 12:24:55 +0200
From:	Hans Schillstrom <hans.schillstrom@...csson.com>
To:	Daniel Lezcano <daniel.lezcano@...e.fr>
CC:	"lvs-devel@...r.kernel.org" <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 ?


On Tue, 2010-08-24 at 12:02 +0200, Daniel Lezcano wrote:
> On 08/24/2010 10:53 AM, Hans Schillstrom wrote:
> > 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().
> >    
> 
> That sounds me familiar ... :)
I have found it, local usage of seq->private.
When the admin part works, (hopefully to morrow) I will send the patch
> 
> > 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.
> >    
> 
> Cool, thanks !
> 
>    -- Daniel
> 
> --

/Hans

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