From: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Development Mailing list
<netfilter-devel@vger.kernel.org>,
Patrick McHardy <kaber@trash.net>
Subject: Re: [nf_tables PATCH 5/5] netfilter: nf_tables: extend NFT_MSG_DELTABLE to support flushing the ruleset
Date: Tue, 26 Aug 2014 13:40:39 +0200 [thread overview]
Message-ID: <CAOkSjBiCxnHFTvuNMSw0-P94WPPeYSJBjoWb6jnKqThFhBoVjQ@mail.gmail.com> (raw)
In-Reply-To: <20140826105322.GA5354@salvia>
On 26 August 2014 12:53, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> On Tue, Aug 26, 2014 at 11:57:01AM +0200, Arturo Borrero Gonzalez wrote:
>> This patch extend the NFT_MSG_DELTABLE call to support flushing the entire
>> ruleset.
>>
>> The options now are:
>> * No family speficied, no table specified: flush all the ruleset.
>> * Family specified, no table specified: flush all tables in the AF.
>> * Family specified, table specified: flush the given table.
>>
[...]
>> @@ -709,21 +775,31 @@ static int nf_tables_deltable(struct sock *nlsk, struct sk_buff *skb,
>> int family = nfmsg->nfgen_family;
>> struct nft_ctx ctx;
>>
>> + if (family == NFPROTO_UNSPEC) {
>> + if (nla[NFTA_TABLE_NAME] != NULL)
>> + return -EINVAL;
>
> We should implement this too. I think you can replace
> nft_flush_ruleset and nft_flush_family by something more generic like:
>
> static int nf_tables_flush(struct net *net, ...)
> {
> ...
>
> list_for_each_entry(afi, &net->nft.af_info, list) {
> if (family != AF_UNSPEC && afi->family != family)
> continue;
>
> list_for_each_entry_safe(table, next, afi->tables, list) {
> if (nla[NFTA_TABLE_NAME] &&
> nla_strcmp(nla[NFTA_TABLE_NAME], table->name) != 0)
> continue;
>
> err = nft_flush_table(table);
> ...
> }
> }
> return err;
> }
>
Ok. I agree.
> You can also skip the nft_ctx_init with this since it's quite empty
> and I guess my proposed nf_tables_flush should take around three
> parameters.
>
All functions take that nft_ctx and fill the needed data for the inner
and later functions (trans allocation, trans commit/abort, event
notifications..). I didn't find a cleaner way to do it, and the
nft_ctx_init() doesn't hurt.
So, I think we still need to use the nft_ctx even with that small
data, don't you?
--
Arturo Borrero González
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-08-26 11:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 9:56 [nf_tables PATCH 0/5] Extended NFT_MSG_DELTABLE Arturo Borrero Gonzalez
2014-08-26 9:56 ` [nf_tables PATCH 1/5] netfilter: nf_tables: refactor rule deletion helper Arturo Borrero Gonzalez
2014-08-26 9:56 ` [nf_tables PATCH 2/5] netfilter: nf_tables: add helper to unregister chain hooks Arturo Borrero Gonzalez
2014-08-26 9:56 ` [nf_tables PATCH 3/5] netfilter: nf_tables: rename nf_table_delrule_by_chain() Arturo Borrero Gonzalez
2014-08-26 9:56 ` [nf_tables PATCH 4/5] netfilter: nf_tables: add helpers to schedule objects deletion Arturo Borrero Gonzalez
2014-08-26 9:57 ` [nf_tables PATCH 5/5] netfilter: nf_tables: extend NFT_MSG_DELTABLE to support flushing the ruleset Arturo Borrero Gonzalez
2014-08-26 10:53 ` Pablo Neira Ayuso
2014-08-26 11:40 ` Arturo Borrero Gonzalez [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=CAOkSjBiCxnHFTvuNMSw0-P94WPPeYSJBjoWb6jnKqThFhBoVjQ@mail.gmail.com \
--to=arturo.borrero.glez@gmail.com \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@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 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).