All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: stable@kernel.org
Cc: Patrick McHardy <kaber@trash.net>,
	netfilter-devel@vger.kernel.org, davem@davemloft.net
Subject: netfilter 00/03: netfilter -stable update
Date: Fri,  6 Jun 2008 19:18:40 +0200 (MEST)	[thread overview]
Message-ID: <20080606171839.28097.47793.sendpatchset@localhost.localdomain> (raw)

[ Sorry for the resend, I forgot to CC netfilter-devel ]

Following are three netfilter patches for -stable, fixing

- a NULL argument to kmem_cache_destroy() in a conntrack error
  path (would cause a BUG_ON)

- incorrect accounting of closed connections in the iptables connlimit match

- incorrect locking in IPv6 connection tracking defragmentation

Please apply, thanks.


 net/ipv6/netfilter/nf_conntrack_reasm.c |    8 +++++---
 net/netfilter/nf_conntrack_expect.c     |    4 ++--
 net/netfilter/xt_connlimit.c            |    3 ++-
 3 files changed, 9 insertions(+), 6 deletions(-)

Alexey Dobriyan (1):
      netfilter: nf_conntrack_expect: fix error path unwind in nf_conntrack_expect_init()

Dong Wei (1):
      netfilter: xt_connlimit: fix accouning when receive RST packet in ESTABLISHED state

Jarek Poplawski (1):
      netfilter: nf_conntrack_ipv6: fix inconsistent lock state in nf_ct_frag6_gather()

             reply	other threads:[~2008-06-06 17:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06 17:18 Patrick McHardy [this message]
2008-06-06 17:18 ` netfilter 01/03: nf_conntrack_expect: fix error path unwind in nf_conntrack_expect_init() Patrick McHardy
2008-06-06 17:18 ` netfilter 02/03: xt_connlimit: fix accouning when receive RST packet in ESTABLISHED state Patrick McHardy
2008-06-06 17:18 ` netfilter 03/03: nf_conntrack_ipv6: fix inconsistent lock state in nf_ct_frag6_gather() Patrick McHardy

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=20080606171839.28097.47793.sendpatchset@localhost.localdomain \
    --to=kaber@trash.net \
    --cc=davem@davemloft.net \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=stable@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 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.