From: pablo@netfilter.org
To: stable@kernel.org
Cc: netfilter-devel@vger.kernel.org
Subject: [PATCH] Netfilter/IPVS updates for stable 3.0 onwards
Date: Thu, 11 Oct 2012 12:00:01 +0200 [thread overview]
Message-ID: <1349949607-12190-1-git-send-email-pablo@netfilter.org> (raw)
From: Pablo Neira Ayuso <pablo@netfilter.org>
Hi!
The following patchset aims to reduce the Netfilter debt with stable 3.0 and
onwards.
The selected six patches are:
07153c6 netfilter: nf_ct_ipv4: packets with wrong ihl are invalid
3f509c6 netfilter: nf_nat_sip: fix incorrect handling of EBUSY for RTCP expectation
f22eb25 netfilter: nf_nat_sip: fix via header translation with multiple parameters
2614f86 netfilter: nf_ct_expect: fix possible access to uninitialized timer
9e33ce4 ipvs: fix oops on NAT reply in br_nf context
82e6bfe netfilter: xt_limit: have r->cost != 0 case work [REQUIRES 7a909ac netfilter: limit, hashlimit: avoid duplicated inline]
I have read stable_rules.txt and I consider they match the requirements.
Please, cherry-pick them. Thanks!
next reply other threads:[~2012-10-11 10:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 10:00 pablo [this message]
2012-10-11 10:00 ` [PATCH 1/6] netfilter: nf_ct_ipv4: packets with wrong ihl are invalid pablo
2012-10-11 10:00 ` [PATCH 2/6] netfilter: nf_nat_sip: fix incorrect handling of EBUSY for RTCP expectation pablo
2012-10-11 10:00 ` [PATCH 3/6] netfilter: nf_nat_sip: fix via header translation with multiple parameters pablo
2012-10-11 10:00 ` [PATCH 4/6] netfilter: nf_ct_expect: fix possible access to uninitialized timer pablo
2012-10-11 10:00 ` [PATCH 5/6] ipvs: fix oops on NAT reply in br_nf context pablo
2012-10-11 10:00 ` [PATCH 6/6] netfilter: xt_limit: have r->cost != 0 case work pablo
2012-10-11 19:08 ` [PATCH] Netfilter/IPVS updates for stable 3.0 onwards David Miller
2012-10-11 19:11 ` David Miller
2012-10-11 21:55 ` Pablo Neira Ayuso
2012-10-11 22:21 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2012-10-11 10:15 pablo
2012-10-11 22:20 ` David Miller
2012-10-14 9:43 ` Ben Hutchings
2012-10-15 23:39 ` Greg KH
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=1349949607-12190-1-git-send-email-pablo@netfilter.org \
--to=pablo@netfilter.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).