From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netfilter-devel@vger.kernel.org,
Serhey Popovych <serhe.popovych@gmail.com>
Subject: Re: [iptables PATCH 1/3] libxtables: Make sure extensions register in revision order
Date: Sat, 3 Oct 2020 13:17:41 +0200 [thread overview]
Message-ID: <20201003111741.GA3035@salvia> (raw)
In-Reply-To: <20200922225341.8976-2-phil@nwl.cc>
Hi Phil,
On Wed, Sep 23, 2020 at 12:53:39AM +0200, Phil Sutter wrote:
> Insert extensions into pending lists in ordered fashion: Group by
> extension name (and, for matches, family) and order groups by descending
> revision number.
>
> This allows to simplify the later full registration considerably. Since
> that involves kernel compatibility checks, the extra cycles here pay off
> eventually.
>
> Signed-off-by: Phil Sutter <phil@nwl.cc>
> ---
> libxtables/xtables.c | 64 +++++++++++++++++++++++++++++++++++++++-----
> 1 file changed, 58 insertions(+), 6 deletions(-)
>
> diff --git a/libxtables/xtables.c b/libxtables/xtables.c
> index 8907ba2069be7..63d0ea5def2d5 100644
> --- a/libxtables/xtables.c
> +++ b/libxtables/xtables.c
> @@ -948,8 +948,14 @@ static void xtables_check_options(const char *name, const struct option *opt)
> }
> }
>
> +static int xtables_match_prefer(const struct xtables_match *a,
> + const struct xtables_match *b);
> +
> void xtables_register_match(struct xtables_match *me)
> {
> + struct xtables_match **pos;
> + bool seen_myself = false;
> +
> if (me->next) {
> fprintf(stderr, "%s: match \"%s\" already registered\n",
> xt_params->program_name, me->name);
> @@ -1001,10 +1007,32 @@ void xtables_register_match(struct xtables_match *me)
> if (me->extra_opts != NULL)
> xtables_check_options(me->name, me->extra_opts);
>
> + /* order into linked list of matches pending full registration */
> + for (pos = &xtables_pending_matches; *pos; pos = &(*pos)->next) {
> + /* NOTE: No extension_cmp() here as we accept all families */
> + if (strcmp(me->name, (*pos)->name) ||
> + me->family != (*pos)->family) {
> + if (seen_myself)
> + break;
> + continue;
> + }
> + seen_myself = true;
> + if (xtables_match_prefer(me, *pos) >= 0)
xtables_match_prefer() evaluates >= 0 if 'me' has higher revision
number than *pos. So list order is: higher revision first.
> + break;
> + }
> + if (!*pos)
> + pos = &xtables_pending_matches;
>
> - /* place on linked list of matches pending full registration */
> - me->next = xtables_pending_matches;
> - xtables_pending_matches = me;
> + me->next = *pos;
This line above is placing 'me' right before the existing match in the list.
> + *pos = me;
This line above only works if *pos is &xtables_pending_matches?
Looking at the in-tree extensions, they are always ordered from lower
to higher (in array definitions).
next prev parent reply other threads:[~2020-10-03 11:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 22:53 [iptables PATCH 0/3] libxtables: Fix for pointless socket() calls Phil Sutter
2020-09-22 22:53 ` [iptables PATCH 1/3] libxtables: Make sure extensions register in revision order Phil Sutter
2020-10-03 11:17 ` Pablo Neira Ayuso [this message]
2020-10-04 14:53 ` Phil Sutter
2020-10-05 22:42 ` Pablo Neira Ayuso
2020-10-06 9:27 ` Phil Sutter
2020-10-06 9:50 ` Pablo Neira Ayuso
2020-10-06 10:13 ` Phil Sutter
2020-10-06 10:48 ` Pablo Neira Ayuso
2020-10-06 12:07 ` [iptables PATCH v2] " Phil Sutter
2020-10-06 23:59 ` Pablo Neira Ayuso
2020-09-22 22:53 ` [iptables PATCH 2/3] libxtables: Simplify pending extension registration Phil Sutter
2020-10-05 23:08 ` Pablo Neira Ayuso
2020-09-22 22:53 ` [iptables PATCH 3/3] libxtables: Register multiple extensions in ascending order Phil Sutter
2020-10-05 23:41 ` Pablo Neira Ayuso
2020-10-06 9:29 ` Phil Sutter
2020-09-23 11:45 ` [iptables PATCH 0/3] libxtables: Fix for pointless socket() calls Pablo Neira Ayuso
2020-09-23 14:30 ` Phil Sutter
2020-10-07 0:02 ` 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=20201003111741.GA3035@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
--cc=serhe.popovych@gmail.com \
/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).