netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: pablo@netfilter.org
To: netfilter-devel@vger.kernel.org
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: [PATCH 0/8] netfilter updates for 3.4-rc5
Date: Mon, 30 Apr 2012 17:16:47 +0200	[thread overview]
Message-ID: <1335799015-2003-1-git-send-email-pablo@netfilter.org> (raw)

From: Pablo Neira Ayuso <pablo@netfilter.org>

Hi David!

This patchset contains the following fixes:

* One fix in the initialization path of the IPVS modules spotted by
  the the trinity syscall fuzz testing tool from Sasha Levin.

* Three patches to address more weak/buggy error handling in the
  initialization path of the IPVS modules from Hans Schillinstrom.

* Fix a regression in the initialization path of ipvs_ctl (introduced in
  2.6.39) due from Julian Anastasov.

* A couple more initialization path robust error checkings from Julian
  Anastasov.

* One silly fix for xt_CT target for the case in which the new
  cttimeout infrastructure is not used, eg. --helper or --notrack,
  by myself.

You can pull these fixes from:

git://1984.lsi.us.es/net master

Thanks!

Hans Schillstrom (3):
  ipvs: null check of net->ipvs in lblc(r) shedulers
  ipvs: take care of return value from protocol init_netns
  ipvs: kernel oops - do_ip_vs_get_ctl

Julian Anastasov (3):
  ipvs: fix crash in ip_vs_control_net_cleanup on unload
  ipvs: add check in ftp for initialized core
  ipvs: reset ipvs pointer in netns

Pablo Neira Ayuso (1):
  netfilter: xt_CT: fix wrong checking in the timeout assignment path

Sasha Levin (1):
  ipvs: Verify that IP_VS protocol has been registered

 include/net/ip_vs.h                   |    4 ++-
 net/netfilter/ipvs/ip_vs_core.c       |   11 +++++++
 net/netfilter/ipvs/ip_vs_ctl.c        |   56 +++++++++++++++++++--------------
 net/netfilter/ipvs/ip_vs_ftp.c        |    2 ++
 net/netfilter/ipvs/ip_vs_lblc.c       |    3 ++
 net/netfilter/ipvs/ip_vs_lblcr.c      |    3 ++
 net/netfilter/ipvs/ip_vs_proto.c      |   38 +++++++++++++++-------
 net/netfilter/ipvs/ip_vs_proto_sctp.c |    5 ++-
 net/netfilter/ipvs/ip_vs_proto_tcp.c  |    5 ++-
 net/netfilter/ipvs/ip_vs_proto_udp.c  |    5 ++-
 net/netfilter/xt_CT.c                 |    2 +-
 11 files changed, 94 insertions(+), 40 deletions(-)

-- 
1.7.9.5


             reply	other threads:[~2012-04-30 15:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-30 15:16 pablo [this message]
2012-04-30 15:16 ` [PATCH 1/8] ipvs: Verify that IP_VS protocol has been registered pablo
2012-04-30 15:16 ` [PATCH 2/8] ipvs: fix crash in ip_vs_control_net_cleanup on unload pablo
2012-04-30 15:16 ` [PATCH 3/8] ipvs: add check in ftp for initialized core pablo
2012-04-30 15:16 ` [PATCH 4/8] ipvs: reset ipvs pointer in netns pablo
2012-04-30 15:16 ` [PATCH 5/8] ipvs: null check of net->ipvs in lblc(r) shedulers pablo
2012-04-30 15:16 ` [PATCH 6/8] ipvs: take care of return value from protocol init_netns pablo
2012-04-30 15:16 ` [PATCH 7/8] ipvs: kernel oops - do_ip_vs_get_ctl pablo
2012-04-30 15:16 ` [PATCH 8/8] netfilter: xt_CT: fix wrong checking in the timeout assignment path pablo
2012-04-30 17:23 ` [PATCH 0/8] netfilter updates for 3.4-rc5 David Miller

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=1335799015-2003-1-git-send-email-pablo@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=davem@davemloft.net \
    --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 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).