From: Simon Horman <horms@verge.net.au>
To: Pablo Neira Ayuso <pablo@netfilter.org>
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>
Subject: Re: [GIT PULL nf] IPVS Fixes for v3.20
Date: Tue, 10 Feb 2015 14:44:32 +0900 [thread overview]
Message-ID: <20150210054432.GC10139@verge.net.au> (raw)
In-Reply-To: <20150210053141.GA3248@salvia>
On Tue, Feb 10, 2015 at 06:31:41AM +0100, Pablo Neira Ayuso wrote:
> On Mon, Feb 09, 2015 at 02:25:07PM +0900, Simon Horman wrote:
> > Hi Pablo,
> >
> > please consider this fix for v3.20
> >
> > This patch prevents the kernel getting into a situation whereby a
> > real-server may not be removed from a heterogeneous IPVS virtual server.
> >
> > This problem was introduced by bc18d37f676f ("ipvs: Allow heterogeneous
> > pools now that we support them") in v3.18. This patch seems appropriate
> > for stable and I have checked that it applies cleanly to both v3.19 and
> > v3.18.6.
> >
> >
> > The following changes since commit 42b5212fee4f57907e9415b18fe19c13e65574bc:
> >
> > xen-netback: stop the guest rx thread after a fatal error (2015-02-02 19:39:04 -0800)
> >
> > are available in the git repository at:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs.git tags/ipvs-fixes-for-v3.20
>
> Pulled, thanks Simon.
Thanks Pablo.
I have an unrelated feature patch for v3.20 queued up.
I'll send a pull request for that shortly.
prev parent reply other threads:[~2015-02-10 5:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 5:25 [GIT PULL nf] IPVS Fixes for v3.20 Simon Horman
2015-02-09 5:25 ` [PATCH nf] ipvs: fix inability to remove a mixed-family RS Simon Horman
2015-02-10 5:31 ` [GIT PULL nf] IPVS Fixes for v3.20 Pablo Neira Ayuso
2015-02-10 5:44 ` Simon Horman [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=20150210054432.GC10139@verge.net.au \
--to=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=pablo@netfilter.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.