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 0/1] IPVS Fixes for v4.11
Date: Fri, 28 Apr 2017 12:03:27 +0200 [thread overview]
Message-ID: <20170428100326.GC13359@verge.net.au> (raw)
In-Reply-To: <20170428095816.6588-1-horms@verge.net.au>
Sorry, I messed this up.
I will repost.
On Fri, Apr 28, 2017 at 11:58:15AM +0200, Simon Horman wrote:
> Hi Pablo,
>
> please consider this fix to IPVS for v4.11.
> Or if it is too late for v4.11 please consider it for v4.12.
> I would also like it considered for stable.
>
> * Explicitly forbid ipv6 service/dest creation if ipv6 mod is disabled
> to avoid oops caused by IPVS accesing IPv6 routing code in such
> circumstances.
>
> The following changes since commit 1debdc8f9ebd07daf140e417b3841596911e0066:
>
> sh_eth: unmap DMA buffers when freeing rings (2017-04-18 22:04:32 -0400)
>
> are available in the git repository at:
>
> http://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs-next.git ipvs-fixes-for-v4.11
>
> for you to fetch changes up to 8f8688b0d483ff06236808ab5fc8bc83c5eaa8d9:
>
> ipvs: explicitly forbid ipv6 service/dest creation if ipv6 mod is disabled (2017-04-24 11:53:55 +0200)
>
> ----------------------------------------------------------------
> Paolo Abeni (1):
> ipvs: explicitly forbid ipv6 service/dest creation if ipv6 mod is disabled
>
> net/netfilter/ipvs/ip_vs_ctl.c | 22 +++++++++++++++++-----
> 1 file changed, 17 insertions(+), 5 deletions(-)
>
> --
> 2.12.2.816.g2cccc81164
>
prev parent reply other threads:[~2017-04-28 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 9:58 [GIT 0/1] IPVS Fixes for v4.11 Simon Horman
2017-04-28 9:58 ` [PATCH 1/1] ipvs: explicitly forbid ipv6 service/dest creation if ipv6 mod is disabled Simon Horman
2017-04-28 10:03 ` 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=20170428100326.GC13359@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 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).