From: Massimiliano Hofer <max@nucleus.it>
To: netfilter-devel@lists.netfilter.org
Subject: [PATCH] priv_data 0/2
Date: Mon, 26 Jun 2006 16:41:46 +0200 [thread overview]
Message-ID: <200606261641.47294.max@nucleus.it> (raw)
Hi,
this is a version of my priv_data patch that updates targets and renames
functions as suggested by Patrick.
Since xt_init_match() and xt_init_target() (formerly xt_check_match() and
xt_check_target()) no longer just check and they needed some argument changes
anyway, I included some more common code previously replicated in
ip_tables.c, ip6_tables.c and arp_tables.c.
Similarly I introduced xt_destroy_match() and xt_destroy_taget().
The resulting patches are larger than I anticipated, but most of the space is
taken by function ranames and argument adjustments.
My previous example with xt_condition still applies (just rename checkentry to
init in struct xt_match).
I tested several combination with iptables, ip6tables and arptables. It can't
make it fail, but I didn't try it with a real world network load. Right now I
don't have a 64 bit machine available for testing (I should be able to use
one in a few days), so I didn't test compat at all.
Testing and comments, as always, are appreciated.
--
Saluti,
Massimiliano Hofer
next reply other threads:[~2006-06-26 14:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 14:41 Massimiliano Hofer [this message]
2006-07-03 18:33 ` [PATCH] priv_data 0/2 Patrick McHardy
2006-07-03 21:05 ` Massimiliano Hofer
2006-07-03 22:58 ` Sven Anders
2006-07-04 0:20 ` Patrick McHardy
2006-07-20 22:38 ` Joakim Axelsson
2006-07-20 23:25 ` Patrick McHardy
2006-07-21 9:29 ` Joakim Axelsson
2006-07-21 9:52 ` Amin Azez
2006-07-22 13:34 ` Patrick McHardy
2006-08-14 14:17 ` Joakim Axelsson
2006-08-14 14:22 ` Patrick McHardy
2006-08-14 15:35 ` Joakim Axelsson
2006-08-14 15:43 ` Patrick McHardy
2006-08-14 16:24 ` xt_quota (Was: [PATCH] priv_data 0/2) Joakim Axelsson
2006-08-14 16:39 ` 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=200606261641.47294.max@nucleus.it \
--to=max@nucleus.it \
--cc=netfilter-devel@lists.netfilter.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.