All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Schillstrom <hans.schillstrom@ericsson.com>
To: Daniel Lezcano <daniel.lezcano@free.fr>
Cc: "lvs-devel@vger.kernel.org" <lvs-devel@vger.kernel.org>,
	"netfilter-devel@vger.kernel.org"
	<netfilter-devel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: IPVS network namespace aware ?
Date: Tue, 24 Aug 2010 12:24:55 +0200	[thread overview]
Message-ID: <1282645495.25529.44.camel@seasc0214.dyn.rnd.as.sw.ericsson.se> (raw)
In-Reply-To: <4C7398CD.7090905@free.fr>


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


      reply	other threads:[~2010-08-24 10:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-06 12:57 IPVS network namespace aware ? Hans Schillstrom
2010-08-06 13:59 ` Simon Horman
2010-08-23 19:21 ` Daniel Lezcano
2010-08-24  8:53   ` Hans Schillstrom
2010-08-24 10:02     ` Daniel Lezcano
2010-08-24 10:24       ` Hans Schillstrom [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1282645495.25529.44.camel@seasc0214.dyn.rnd.as.sw.ericsson.se \
    --to=hans.schillstrom@ericsson.com \
    --cc=daniel.lezcano@free.fr \
    --cc=lvs-devel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.