netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Cree <ecree@solarflare.com>
To: Florian Westphal <fw@strlen.de>, <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH v2 nf-next] netfilter: add and use nf_hook_slow_list()
Date: Thu, 10 Oct 2019 23:41:38 +0100	[thread overview]
Message-ID: <2d9864c9-95d2-02c2-b256-85a07c2b2232@solarflare.com> (raw)
In-Reply-To: <20191010223037.10811-1-fw@strlen.de>

On 10/10/2019 23:30, Florian Westphal wrote:
> NF_HOOK_LIST now only works for ipv4 and ipv6, as those are the only
> callers.
...
> +
> +     rcu_read_lock();
> +     switch (pf) {
> +     case NFPROTO_IPV4:
> +             hook_head = rcu_dereference(net->nf.hooks_ipv4[hook]);
> +             break;
> +     case NFPROTO_IPV6:
> +             hook_head = rcu_dereference(net->nf.hooks_ipv6[hook]);
> +             break;
> +     default:
> +             WARN_ON_ONCE(1);
> +             break;
>       }
Would it not make sense instead to abstract out the switch in nf_hook()
 into, say, an inline function that could be called from here?  That
 would satisfy SPOT and also save updating this code if new callers of
 NF_HOOK_LIST are added in the future.

(Sorry I didn't spot this the first time around; I don't know the NF
 code all that well.)

-Ed
The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error, please notify the sender immediately and delete the message. Unless you are an addressee (or authorized to receive for an addressee), you may not use, copy or disclose to anyone this message or any information contained in this message. The unauthorized use, disclosure, copying or alteration of this message is strictly prohibited.

  reply	other threads:[~2019-10-10 22:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-10 22:30 [PATCH v2 nf-next] netfilter: add and use nf_hook_slow_list() Florian Westphal
2019-10-10 22:41 ` Edward Cree [this message]
2019-10-10 22:54   ` Florian Westphal
2019-10-14 11:02     ` Pablo Neira Ayuso
2019-10-14 13:56       ` Edward Cree
2019-10-17 10:20 ` 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=2d9864c9-95d2-02c2-b256-85a07c2b2232@solarflare.com \
    --to=ecree@solarflare.com \
    --cc=fw@strlen.de \
    --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 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).