netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver <olipro@8.c.9.b.0.7.4.0.1.0.0.2.ip6.arpa>
To: netfilter-devel@vger.kernel.org
Subject: Git commits possibly suitable for 3.8-stable tree?
Date: Sat, 20 Apr 2013 20:19:01 +0200	[thread overview]
Message-ID: <20098583.RM2dngnsmy@gentoovm> (raw)

Hi,

Would any of the following mainline commits be appropriate for cherry-picking 
into the 3.8 stable tree?

c2d421e netfilter: nf_nat: fix race when unloading protocol modules
6eb4c7e netfilter: ipset: hash:*net*: nomatch flag not excluded on set resize
02f815c netfilter: ipset: list:set: fix reference counter update
3a7b21e netfilter: nf_ct_sip: don't drop packets with offsets pointing outside 
the packet
906b1c3 netfilter: ip6t_NPT: Fix translation for non-multiple of 32 prefix 
lengths
bae99f7 netfilter: nfnetlink_queue: fix incorrect initialization of copy range 
field
dd82088 netfilter: ipset: "Directory not empty" error message
cf1c4a0 netfilter: ipset: timeout values corrupted on set resize
442fad9 netfilter: ctnetlink: don't permit ct creation with random tuple
d9e8565 netfilter ip6table_mangle: Use ipv6_addr_equal() where appropriate.
29e3b16 netfilter ipset: Use ipv6_addr_equal() where appropriate.

Additionally there are these two related commits:

124dff0 netfilter: don't reset nf_trace in nf_reset()
130549f netfilter: reset nf_trace in nf_reset

Kind Regards,

Oliver

             reply	other threads:[~2013-04-20 18:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-20 18:19 Oliver [this message]
2013-04-21  9:14 ` Git commits possibly suitable for 3.8-stable tree? Pablo Neira Ayuso

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=20098583.RM2dngnsmy@gentoovm \
    --to=olipro@8.c.9.b.0.7.4.0.1.0.0.2.ip6.arpa \
    --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).