From: Aaron Conole <aconole@bytheb.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf,v2] netfilter: nf_queue: don't re-enter same hook on packet reinjection
Date: Mon, 17 Oct 2016 11:23:01 -0400 [thread overview]
Message-ID: <f7tzim3j8yy.fsf@redhat.com> (raw)
In-Reply-To: <1476441446-19611-1-git-send-email-pablo@netfilter.org> (Pablo Neira Ayuso's message of "Fri, 14 Oct 2016 12:37:26 +0200")
Pablo Neira Ayuso <pablo@netfilter.org> writes:
> Make sure we skip the current hook from where the packet was enqueued,
> otherwise the packets gets enqueued over and over again.
>
> Fixes: e3b37f11e6e4 ("netfilter: replace list_head with single linked list")
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> ---
> v2: Make sure next hook is non-null, otherwise we are at the end of the
> hook list and we can skip nf_iterate().
>
> net/netfilter/nf_queue.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/net/netfilter/nf_queue.c b/net/netfilter/nf_queue.c
> index 96964a0070e1..691e713d70f5 100644
> --- a/net/netfilter/nf_queue.c
> +++ b/net/netfilter/nf_queue.c
> @@ -185,8 +185,9 @@ void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict)
> }
>
> entry->state.thresh = INT_MIN;
> + hook_entry = rcu_dereference(hook_entry->next);
>
> - if (verdict == NF_ACCEPT) {
> + if (hook_entry && verdict == NF_ACCEPT) {
> next_hook:
> verdict = nf_iterate(skb, &entry->state, &hook_entry);
> }
ACK. I thought switch case below could have a problem, but re-checked
the first nf_queue leg, and it seems okay.
-Aaron
next prev parent reply other threads:[~2016-10-17 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 10:37 [PATCH nf,v2] netfilter: nf_queue: don't re-enter same hook on packet reinjection Pablo Neira Ayuso
2016-10-17 15:23 ` Aaron Conole [this message]
2016-10-17 17:03 ` Pablo Neira Ayuso
2016-10-17 19:29 ` Aaron Conole
2016-10-18 15:34 ` Pablo Neira Ayuso
2016-10-18 15:45 ` Florian Westphal
2016-10-18 19:20 ` 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=f7tzim3j8yy.fsf@redhat.com \
--to=aconole@bytheb.org \
--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 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.