From: Aaron Conole <aconole@bytheb.org>
To: netdev@vger.kernel.org
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [RFC nf-next 1/3] netfilter: bridge: add and use br_nf_hook_thresh
Date: Wed, 22 Jun 2016 17:43:11 -0400 [thread overview]
Message-ID: <f7t1t3ozyq8.fsf@redhat.com> (raw)
In-Reply-To: <1466631271-10737-2-git-send-email-aconole@bytheb.org> (Aaron Conole's message of "Wed, 22 Jun 2016 17:34:29 -0400")
Aaron Conole <aconole@bytheb.org> writes:
> From: Florian Westphal <fw@strlen.de>
>
> This replaces the last uses of NF_HOOK_THRESH().
> Followup patch will remove it and rename nf_hook_thresh.
>
> The reason is that inet (non-bridge) netfilter no longer invokes the
> hooks from hooks, so we do no longer need the thresh value to skip hooks
> with a lower priority.
>
> The bridge netfilter however may need to do this. br_nf_hook_thresh is a
> wrapper that is supposed to do this, i.e. only call hooks with a
> priority that exceeds NF_BR_PRI_BRNF.
>
> It's used only in the recursion cases of br_netfilter.
>
> Signed-off-by: Florian Westphal <fw@strlen.de>
> Signed-off-by: Aaron Conole <aconole@redhat.com>
> ---
I will make sure to fix the address in this patch. Apologies.
next prev parent reply other threads:[~2016-06-22 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 21:34 [RFC nf-next 0/3] Compact netfilter hooks list Aaron Conole
2016-06-22 21:34 ` [RFC nf-next 1/3] netfilter: bridge: add and use br_nf_hook_thresh Aaron Conole
2016-06-22 21:43 ` Aaron Conole [this message]
2016-06-22 21:34 ` [RFC nf-next 2/3] netfilter: call nf_hook_state_init with rcu_read_lock held Aaron Conole
2016-06-22 21:34 ` [RFC nf-next 3/3] netfilter: replace list_head with single linked list Aaron Conole
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=f7t1t3ozyq8.fsf@redhat.com \
--to=aconole@bytheb.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.