From: Patrick McHardy <kaber@trash.net>
To: Alexey Dobriyan <adobriyan@sw.ru>
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
devel@openvz.org
Subject: Re: [PATCH 1/3] netns netfilter: semi-rewrite of /proc/net/foo_tables_*
Date: Wed, 30 Jan 2008 16:17:10 +0100 [thread overview]
Message-ID: <47A094F6.6010406@trash.net> (raw)
In-Reply-To: <20080125164314.GE6028@localhost.sw.ru>
Alexey Dobriyan wrote:
> Argh, there are many small but still wrong things with /proc/net/*_tables_*
> so I decided to do overhaul simultaneously making it more suitable for
> per-netns /proc/net/*_tables_* implementation.
>
> Fix
> a) xt_get_idx() duplicating now standard seq_list_start/seq_list_next
> iterators
> b) tables/matches/targets list was chosen again and again on every ->next
> c) multiple useless "af >= NPROTO" checks -- we simple don't supply invalid
> AFs there and registration function should BUG_ON instead.
>
> Regardless, the one in ->next() is the most useless -- ->next doesn't
> run at all if ->start fails.
> d) Don't use mutex_lock_interruptible() -- it can fail and ->stop is
> executed even if ->start failed, so unlock without lock is possible.
>
> As side effect, streamline code by splitting xt_tgt_ops into xt_target_ops,
> xt_matches_ops, xt_tables_ops.
>
> xt_tables_ops hooks will be changed by per-netns code. Code of
> xt_matches_ops, xt_target_ops is identical except the list chosen for
> iterating, but I think consolidating code for two files not worth it
> given "<< 16" hacks needed for it.
>
> Signed-off-by: Alexey Dobriyan <adobriyan@sw.ru>
Applied, and I also removed the now unused TABLE/TARGET/MATCH enum.
prev parent reply other threads:[~2008-01-30 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 16:43 [PATCH 1/3] netns netfilter: semi-rewrite of /proc/net/foo_tables_* Alexey Dobriyan
2008-01-30 15:17 ` Patrick McHardy [this message]
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=47A094F6.6010406@trash.net \
--to=kaber@trash.net \
--cc=adobriyan@sw.ru \
--cc=devel@openvz.org \
--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 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.