From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Simon Horman <horms@verge.net.au>
Cc: lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org,
Wensong Zhang <wensong@linux-vs.org>,
Julian Anastasov <ja@ssi.bg>,
Hans Schillstrom <hans.schillstrom@ericsson.com>,
Jesper Dangaard Brouer <brouer@redhat.com>
Subject: Re: [PATCH 3/3] ipvs: fix oops in ip_vs_dst_event on rmmod
Date: Tue, 17 Jul 2012 12:08:47 +0200 [thread overview]
Message-ID: <20120717100847.GB3812@1984> (raw)
In-Reply-To: <1341965963-7275-4-git-send-email-horms@verge.net.au>
On Wed, Jul 11, 2012 at 09:19:23AM +0900, Simon Horman wrote:
> From: Julian Anastasov <ja@ssi.bg>
>
> After commit 39f618b4fd95ae243d940ec64c961009c74e3333 (3.4)
> "ipvs: reset ipvs pointer in netns" we can oops in
> ip_vs_dst_event on rmmod ip_vs because ip_vs_control_cleanup
> is called after the ipvs_core_ops subsys is unregistered and
> net->ipvs is NULL. Fix it by exiting early from ip_vs_dst_event
> if ipvs is NULL. It is safe because all services and dests
> for the net are already freed.
Applied, thanks.
next prev parent reply other threads:[~2012-07-17 10:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 0:19 [GIT PULL nf] IPVS Simon Horman
2012-07-11 0:19 ` [PATCH 1/3] ipvs: fix oops on NAT reply in br_nf context Simon Horman
2012-07-17 10:08 ` Pablo Neira Ayuso
2012-07-11 0:19 ` [PATCH 2/3] ipvs: add missing lock in ip_vs_ftp_init_conn() Simon Horman
2012-07-16 21:07 ` Pablo Neira Ayuso
2012-07-17 2:34 ` Xiaotian Feng
2012-07-17 5:14 ` Simon Horman
[not found] ` <CAJn8CcEChmrFvASChJfj7qK8F-my79fn+-G8ttst02Sts15y6Q@mail.gmail.com>
2012-07-17 9:46 ` Pablo Neira Ayuso
2012-07-11 0:19 ` [PATCH 3/3] ipvs: fix oops in ip_vs_dst_event on rmmod Simon Horman
2012-07-17 10:08 ` Pablo Neira Ayuso [this message]
2012-07-17 10:14 ` [GIT PULL nf] IPVS Pablo Neira Ayuso
2012-07-17 13:50 ` Simon Horman
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=20120717100847.GB3812@1984 \
--to=pablo@netfilter.org \
--cc=brouer@redhat.com \
--cc=hans.schillstrom@ericsson.com \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--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 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.