From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Christian Brauner <christian@brauner.io>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
bridge@lists.linux-foundation.org, tyhicks@canonical.com,
kadlec@blackhole.kfki.hu, fw@strlen.de,
roopa@cumulusnetworks.com, nikolay@cumulusnetworks.com,
linux-kernel@vger.kernel.org, richardrose@google.com,
vapier@chromium.org, bhthompson@google.com,
smbarber@chromium.org, joelhockey@chromium.org,
ueberall@themenzentrisch.de
Subject: Re: [PATCH net-next v1 1/1] br_netfilter: namespace bridge netfilter sysctls
Date: Mon, 10 Jun 2019 19:41:36 +0200 [thread overview]
Message-ID: <20190610174136.p3fbcbn33en5bb7f@salvia> (raw)
In-Reply-To: <20190609162304.3388-2-christian@brauner.io>
Thanks for updating this patch to use struct brnf_net.
A few comments below.
On Sun, Jun 09, 2019 at 06:23:04PM +0200, Christian Brauner wrote:
[...]
> diff --git a/include/net/netfilter/br_netfilter.h b/include/net/netfilter/br_netfilter.h
> index 89808ce293c4..302fcd3aade2 100644
> --- a/include/net/netfilter/br_netfilter.h
> +++ b/include/net/netfilter/br_netfilter.h
> @@ -85,17 +82,42 @@ static inline __be16 vlan_proto(const struct sk_buff *skb)
> return 0;
> }
>
> -#define IS_VLAN_IP(skb) \
> - (vlan_proto(skb) == htons(ETH_P_IP) && \
> - brnf_filter_vlan_tagged)
> +static inline bool is_vlan_ip(const struct sk_buff *skb, const struct net *net)
> +{
I like this conversion from macro to static inline a lot.
But if you let me ask for one more change, would you split this in two
patches? One to replace #defines by static inline.
Then, second patch introduces the sysctl update you need.
It will make it easier for me to review.
[...]
> +static inline bool is_vlan_ipv6(const struct sk_buff *skb,
> + const struct net *net)
> +{
> +#ifdef CONFIG_SYSCTL
Probably we can reduce #ifdef pollution a bit if you always add
'filter_vlan_tagged' and other fields to the brnf_net structure. No
matter if CONFIG_SYSCTL is set on or off. I think it's worth consuming
a bit more memory to simplify this code, so both CONFIG_SYSCTL=y and
CONFIG_SYSCTL=n run the same codepath.
Most vendors will just turn on to CONFIG_SYSCTL=y, and I don't think
it's worth the extra code for the CONFIG_SYSCTL=n case.
> + struct brnf_net *brnet = net_generic(net, brnf_net_id);
> +
> + return (vlan_proto(skb) == htons(ETH_P_IPV6) &&
> + brnet->filter_vlan_tagged);
> +#else
> + return (vlan_proto(skb) == htons(ETH_P_IPV6));
BTW, I think parens are not needed, ie.
return vlan_proto(skb) == htons(ETH_P_IPV6);
should be fine?
Thanks!
next prev parent reply other threads:[~2019-06-10 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 16:23 [PATCH net-next v1 0/1] br_netfilter: enable in non-initial netns Christian Brauner
2019-06-09 16:23 ` [PATCH net-next v1 1/1] br_netfilter: namespace bridge netfilter sysctls Christian Brauner
2019-06-10 17:41 ` Pablo Neira Ayuso [this message]
2019-06-10 20:51 ` Christian Brauner
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=20190610174136.p3fbcbn33en5bb7f@salvia \
--to=pablo@netfilter.org \
--cc=bhthompson@google.com \
--cc=bridge@lists.linux-foundation.org \
--cc=christian@brauner.io \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=joelhockey@chromium.org \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=richardrose@google.com \
--cc=roopa@cumulusnetworks.com \
--cc=smbarber@chromium.org \
--cc=tyhicks@canonical.com \
--cc=ueberall@themenzentrisch.de \
--cc=vapier@chromium.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