From: kaber@trash.net
To: davem@davemloft.net
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH 0/2] netfilter: netfilter fixes
Date: Mon, 31 May 2010 18:14:45 +0200 [thread overview]
Message-ID: <1275322487-19026-1-git-send-email-kaber@trash.net> (raw)
the following two patches fix two problems with the recent introduction of
a seperately allocated jumpstack for xtables rulesets:
- a memory leak when registering new tables, from Xiaotian Feng
- performance degradation caused by not using per-CPU allocations
for the jumpstack, from Eric
Please apply or pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/kaber/nf-2.6.git master
Thanks!
next reply other threads:[~2010-05-31 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 16:14 kaber [this message]
2010-05-31 16:14 ` [PATCH 1/2] netfilter: don't xt_jumpstack_alloc twice in xt_register_table kaber
2010-05-31 16:14 ` [PATCH 2/2] netfilter: xtables: stackptr should be percpu kaber
2010-06-01 6:45 ` [PATCH 0/2] netfilter: netfilter fixes David Miller
-- strict thread matches above, loose matches on Subject: below --
2010-11-12 15:19 kaber
2010-11-12 19:07 ` 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=1275322487-19026-1-git-send-email-kaber@trash.net \
--to=kaber@trash.net \
--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).