From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Felix Fietkau <nbd@nbd.name>
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 2/4] netfilter: nft_flow_offload: skip dst neigh lookup for ppp devices
Date: Mon, 9 May 2022 08:26:08 +0200 [thread overview]
Message-ID: <Yni0AIc06fBELtXz@salvia> (raw)
In-Reply-To: <20220506131841.3177-2-nbd@nbd.name>
Series LGTM.
Would you repost adding Fixes: tag and target nf tree?
Thanks.
On Fri, May 06, 2022 at 03:18:39PM +0200, Felix Fietkau wrote:
> The dst entry does not contain a valid hardware address, so skip the lookup
> in order to avoid running into errors here.
> The proper hardware address is filled in from nft_dev_path_info
>
> Signed-off-by: Felix Fietkau <nbd@nbd.name>
> ---
> net/netfilter/nft_flow_offload.c | 22 +++++++++++++---------
> 1 file changed, 13 insertions(+), 9 deletions(-)
>
> diff --git a/net/netfilter/nft_flow_offload.c b/net/netfilter/nft_flow_offload.c
> index 900d48c810a1..d88de26aad75 100644
> --- a/net/netfilter/nft_flow_offload.c
> +++ b/net/netfilter/nft_flow_offload.c
> @@ -36,6 +36,15 @@ static void nft_default_forward_path(struct nf_flow_route *route,
> route->tuple[dir].xmit_type = nft_xmit_type(dst_cache);
> }
>
> +static bool nft_is_valid_ether_device(const struct net_device *dev)
> +{
> + if (!dev || (dev->flags & IFF_LOOPBACK) || dev->type != ARPHRD_ETHER ||
> + dev->addr_len != ETH_ALEN || !is_valid_ether_addr(dev->dev_addr))
> + return false;
> +
> + return true;
> +}
> +
> static int nft_dev_fill_forward_path(const struct nf_flow_route *route,
> const struct dst_entry *dst_cache,
> const struct nf_conn *ct,
> @@ -47,6 +56,9 @@ static int nft_dev_fill_forward_path(const struct nf_flow_route *route,
> struct neighbour *n;
> u8 nud_state;
>
> + if (!nft_is_valid_ether_device(dev))
> + goto out;
> +
> n = dst_neigh_lookup(dst_cache, daddr);
> if (!n)
> return -1;
> @@ -60,6 +72,7 @@ static int nft_dev_fill_forward_path(const struct nf_flow_route *route,
> if (!(nud_state & NUD_VALID))
> return -1;
>
> +out:
> return dev_fill_forward_path(dev, ha, stack);
> }
>
> @@ -78,15 +91,6 @@ struct nft_forward_info {
> enum flow_offload_xmit_type xmit_type;
> };
>
> -static bool nft_is_valid_ether_device(const struct net_device *dev)
> -{
> - if (!dev || (dev->flags & IFF_LOOPBACK) || dev->type != ARPHRD_ETHER ||
> - dev->addr_len != ETH_ALEN || !is_valid_ether_addr(dev->dev_addr))
> - return false;
> -
> - return true;
> -}
> -
> static void nft_dev_path_info(const struct net_device_path_stack *stack,
> struct nft_forward_info *info,
> unsigned char *ha, struct nf_flowtable *flowtable)
> --
> 2.35.1
>
next prev parent reply other threads:[~2022-05-09 6:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 13:18 [PATCH 1/4] netfilter: flowtable: fix excessive hw offload attempts after failure Felix Fietkau
2022-05-06 13:18 ` [PATCH 2/4] netfilter: nft_flow_offload: skip dst neigh lookup for ppp devices Felix Fietkau
2022-05-09 6:26 ` Pablo Neira Ayuso [this message]
2022-05-09 12:28 ` Felix Fietkau
2022-05-06 13:18 ` [PATCH 3/4] net: fix dev_fill_forward_path with pppoe + bridge Felix Fietkau
2022-05-06 13:18 ` [PATCH 4/4] netfilter: nft_flow_offload: fix offload with pppoe + vlan Felix Fietkau
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=Yni0AIc06fBELtXz@salvia \
--to=pablo@netfilter.org \
--cc=nbd@nbd.name \
--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 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).