From: Patrick McHardy <kaber@trash.net>
To: stable@kernel.org
Cc: netdev@vger.kernel.org, Patrick McHardy <kaber@trash.net>,
netfilter-devel@vger.kernel.org, davem@davemloft.net
Subject: netfilter 00/02: netfilter -stable fixes
Date: Thu, 12 Feb 2009 08:07:35 +0100 (MET) [thread overview]
Message-ID: <20090212070732.4876.43180.sendpatchset@x2.localnet> (raw)
These patches against the last -stable version fix two netfilter bugs:
- IPv6 conntrack incorrectly created inverted tuples for Node
Information Requests
- the sctp match doesn't work at all when matching on the entire
chunkmap
Please apply, thanks.
net/ipv6/netfilter/nf_conntrack_proto_icmpv6.c | 4 ++--
net/netfilter/xt_sctp.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
Eric Leblond (1):
netfilter: fix tuple inversion for Node information request
Qu Haoran (1):
netfilter: xt_sctp: sctp chunk mapping doesn't work
next reply other threads:[~2009-02-12 7:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 7:07 Patrick McHardy [this message]
2009-02-12 7:07 ` netfilter 01/02: fix tuple inversion for Node information request Patrick McHardy
2009-02-12 7:07 ` netfilter 02/02: xt_sctp: sctp chunk mapping doesn't work 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=20090212070732.4876.43180.sendpatchset@x2.localnet \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--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 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).