From: Simon Horman <horms@verge.net.au>
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: Hans Schillstrom <hans.schillstrom@ericsson.com>,
ja@ssi.bg, wensong@linux-vs.org, rohara@redhat.com,
lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, hans@schillstrom.com
Subject: Re: [v2 PATCH 1/1] ipvs: kernel oops - do_ip_vs_get_ctl
Date: Thu, 26 Apr 2012 18:05:20 +0900 [thread overview]
Message-ID: <20120426090520.GA5801@verge.net.au> (raw)
In-Reply-To: <1335427841.3131.28.camel@t520>
On Thu, Apr 26, 2012 at 10:10:41AM +0200, Jesper Dangaard Brouer wrote:
> On Thu, 2012-04-26 at 07:47 +0200, Hans Schillstrom wrote:
> > Change order of init so netns init is ready
> > when register ioctl and netlink.
> >
> > Ver2
> > Whitespace fixes and __init added.
> >
> > Reported-by: "Ryan O'Hara" <rohara@redhat.com>
> > Signed-off-by: Hans Schillstrom <hans.schillstrom@ericsson.com>
>
> Looks good, interdiff says you fixed up things, and I have tested it
> against the net tree, good work :-)
>
> Is this a stable tree candidate?
Yes, I think so.
I now have the following 7 changes in my ipvs tree on kernel.org.
The last two are already in Pablo's net tree and I intend
to send a pull request for the remaining 5 soon.
It is my opinion that all 7 patches are stable tree material.
ipvs: kernel oops - do_ip_vs_get_ctl
ipvs: take care of return value from protocol init_netns
ipvs: null check of net->ipvs in lblc(r) shedulers
ipvs: reset ipvs pointer in netns
ipvs: add check in ftp for initialized core
ipvs: fix crash in ip_vs_control_net_cleanup on unload
ipvs: Verify that IP_VS protocol has been registered
next prev parent reply other threads:[~2012-04-26 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 5:47 [v2 PATCH 1/1] ipvs: kernel oops - do_ip_vs_get_ctl Hans Schillstrom
2012-04-26 8:10 ` Jesper Dangaard Brouer
2012-04-26 9:05 ` Simon Horman [this message]
2012-04-26 15:26 ` Pablo Neira Ayuso
2012-04-26 8:11 ` Julian Anastasov
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=20120426090520.GA5801@verge.net.au \
--to=horms@verge.net.au \
--cc=brouer@redhat.com \
--cc=hans.schillstrom@ericsson.com \
--cc=hans@schillstrom.com \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=rohara@redhat.com \
--cc=wensong@linux-vs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).