linux.git/net/core/flow_offload.c, branch v5.19

netfilter: nf_tables: bail out early if hardware offload is not supported

2022-06-06T17:19:15+00:00

If user requests for NFT_CHAIN_HW_OFFLOAD, then check if either device
provides the .ndo_setup_tc interface or there is an indirect flow block
that has been registered. Otherwise, bail out early from the preparation
phase. Moreover, validate that family == NFPROTO_NETDEV and hook is
NF_NETDEV_INGRESS.

Fixes: c9626a2cbdb2 ("netfilter: nf_tables: add hardware offload support")
Signed-off-by: Pablo Neira Ayuso

flow_offload: add reoffload process to update hw_count

2021-12-19T14:08:48+00:00

Add reoffload process to update hw_count when driver
is inserted or removed.

We will delete the action if it is with skip_sw flag and
not offloaded to any hardware in reoffload process.

When reoffloading actions, we still offload the actions
that are added independent of filters.

Signed-off-by: Baowen Zheng 
Signed-off-by: Louis Peens 
Signed-off-by: Simon Horman 
Signed-off-by: David S. Miller

flow_offload: allow user to offload tc action to net device

2021-12-19T14:08:48+00:00

Use flow_indr_dev_register/flow_indr_dev_setup_offload to
offload tc action.

We need to call tc_cleanup_flow_action to clean up tc action entry since
in tc_setup_action, some actions may hold dev refcnt, especially the mirror
action.

Signed-off-by: Baowen Zheng 
Signed-off-by: Louis Peens 
Signed-off-by: Simon Horman 
Signed-off-by: David S. Miller

net: Fix offloading indirect devices dependency on qdisc order creation

2021-08-19T12:19:30+00:00

Currently, when creating an ingress qdisc on an indirect device before
the driver registered for callbacks, the driver will not have a chance
to register its filter configuration callbacks.

To fix that, modify the code such that it keeps track of all the ingress
qdiscs that call flow_indr_dev_setup_offload(). When a driver calls
flow_indr_dev_register(),  go through the list of tracked ingress qdiscs
and call the driver callback entry point so as to give it a chance to
register its callback.

Reviewed-by: Jiri Pirko 
Signed-off-by: Eli Cohen 
Signed-off-by: David S. Miller

net/core: Remove unused field from struct flow_indr_dev

2021-08-19T12:19:30+00:00

rcu field is not used. Remove it.

Reviewed-by: Jiri Pirko 
Signed-off-by: Eli Cohen 
Signed-off-by: David S. Miller

net: flow_offload: Fix memory leak for indirect flow block

2020-12-10T00:08:33+00:00

The offending commit introduces a cleanup callback that is invoked
when the driver module is removed to clean up the tunnel device
flow block. But it returns on the first iteration of the for loop.
The remaining indirect flow blocks will never be freed.

Fixes: 1fac52da5942 ("net: flow_offload: consolidate indirect flow_block infrastructure")
CC: Pablo Neira Ayuso 
Signed-off-by: Chris Mi 
Reviewed-by: Roi Dayan

Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net

2020-07-26T00:49:04+00:00

The UDP reuseport conflict was a little bit tricky.

The net-next code, via bpf-next, extracted the reuseport handling
into a helper so that the BPF sk lookup code could invoke it.

At the same time, the logic for reuseport handling of unconnected
sockets changed via commit efc6b6f6c3113e8b203b9debfb72d81e0f3dcace
which changed the logic to carry on the reuseport result into the
rest of the lookup loop if we do not return immediately.

This requires moving the reuseport_has_conns() logic into the callers.

While we are here, get rid of inline directives as they do not belong
in foo.c files.

The other changes were cases of more straightforward overlapping
modifications.

Signed-off-by: David S. Miller

flow_offload: Move rhashtable inclusion to the source file

2020-07-24T22:17:22+00:00

I noticed that touching linux/rhashtable.h causes lib/vsprintf.c to
be rebuilt.  This dependency came through a bogus inclusion in the
file net/flow_offload.h.  This patch moves it to the right place.

This patch also removes a lingering rhashtable inclusion in cls_api
created by the same commit.

Fixes: 4e481908c51b ("flow_offload: move tc indirect block to...")
Signed-off-by: Herbert Xu 
Signed-off-by: David S. Miller

net: sched: Pass qdisc reference in struct flow_block_offload

2020-07-14T00:22:21+00:00

Previously, shared blocks were only relevant for the pseudo-qdiscs ingress
and clsact. Recently, a qevent facility was introduced, which allows to
bind blocks to well-defined slots of a qdisc instance. RED in particular
got two qevents: early_drop and mark. Drivers that wish to offload these
blocks will be sent the usual notification, and need to know which qdisc it
is related to.

To that end, extend flow_block_offload with a "sch" pointer, and initialize
as appropriate. This prompts changes in the indirect block facility, which
now tracks the scheduler in addition to the netdevice. Update signatures of
several functions similarly.

Signed-off-by: Petr Machata 
Signed-off-by: David S. Miller

net: flow_offload: fix flow_indr_dev_unregister path

2020-06-20T03:12:58+00:00

If the representor is removed, then identify the indirect flow_blocks
that need to be removed by the release callback and the port representor
structure. To identify the port representor structure, a new
indr.cb_priv field needs to be introduced. The flow_block also needs to
be removed from the driver list from the cleanup path.

Fixes: 1fac52da5942 ("net: flow_offload: consolidate indirect flow_block infrastructure")

Signed-off-by: wenxu 
Signed-off-by: David S. Miller