From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] netfilter: xtables: inclusion of xt_condition
Date: Thu, 22 Apr 2010 13:14:50 +0200 [thread overview]
Message-ID: <4BD02FAA.7000207@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.01.1004220100530.6257@obet.zrqbmnf.qr>
This looks better, thanks. A few remaining questions about things
I missed previously:
Jan Engelhardt wrote:
> +static int condition_mt_check(const struct xt_mtchk_param *par)
> +{
> + ...
> + /* Create the condition variable's proc file entry. */
> + var->status_proc = create_proc_entry(info->name, condition_list_perms,
> + proc_net_condition);
proc_net_condition is a global variable, so this won't work for
namespaces. What the code does is reinitialize it when instantiating
a new namespace, so it will always point to the last instantiated
namespace.
The same problem exists for the condition_list, each namespace
should only be able to access its own conditions.
> +static struct xt_match condition_mt_reg __read_mostly = {
> + .name = "condition",
> + .revision = 1,
Why are we starting with revision 1?
> + .family = NFPROTO_UNSPEC,
> + .matchsize = sizeof(struct xt_condition_mtinfo),
> + .match = condition_mt,
> + .checkentry = condition_mt_check,
> + .destroy = condition_mt_destroy,
> + .me = THIS_MODULE,
> +};
next prev parent reply other threads:[~2010-04-22 11:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 13:33 nf-next: condition Jan Engelhardt
2010-04-21 13:33 ` [PATCH] netfilter: xtables: inclusion of xt_condition Jan Engelhardt
2010-04-21 13:39 ` Patrick McHardy
2010-04-22 0:05 ` Jan Engelhardt
2010-04-22 10:55 ` Patrick McHardy
2010-04-22 11:14 ` Patrick McHardy [this message]
2010-04-22 11:24 ` Patrick McHardy
2010-04-22 11:27 ` Jan Engelhardt
2010-04-22 11:29 ` Patrick McHardy
2010-04-22 11:33 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2010-07-16 11:10 Luciano Coelho
2010-07-16 11:20 ` Jan Engelhardt
2010-07-16 11:31 ` Luciano Coelho
2010-07-16 11:54 ` Jan Engelhardt
2010-07-16 12:16 ` Luciano Coelho
2010-07-16 19:14 ` Jan Engelhardt
2010-07-17 6:32 Luciano.Coelho
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=4BD02FAA.7000207@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--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).