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: Wed, 21 Apr 2010 15:39:41 +0200 [thread overview]
Message-ID: <4BCF001D.4090304@trash.net> (raw)
In-Reply-To: <1271856792-20872-2-git-send-email-jengelh@medozas.de>
Jan Engelhardt wrote:
> xt_condition can be used by userspace to influence decisions in rules
> by means of togglable variables without having to reload the entire
> ruleset.
> +
> + var->refcount = 1;
> + var->enabled = false;
> + var->status_proc->data = var;
> + wmb();
Jan, while I'm pretty patient, I don't appreciate having to repeat
the same thing multiple times:
>> Please always comment the use of memory barriers.
> +static int __net_init condnet_mt_init(struct net *net)
> +{
> + int ret;
> +
> + proc_net_condition = proc_mkdir(dir_name, net->proc_net);
> + if (proc_net_condition == NULL)
> + return -EACCES;
> +
> + ret = xt_register_match(&condition_mt_reg);
This is really starting to annoy me. Please read what I wrote,
take your time, test the patch and then resend it.
next prev parent reply other threads:[~2010-04-21 13:39 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 [this message]
2010-04-22 0:05 ` Jan Engelhardt
2010-04-22 10:55 ` Patrick McHardy
2010-04-22 11:14 ` Patrick McHardy
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=4BCF001D.4090304@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).