| Message ID | cover.1674233458.git.dcaratti@redhat.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | net/sched: use the backlog for nested mirred ingress | expand |
Hello: This series was applied to netdev/net-next.git (master) by Paolo Abeni <pabeni@redhat.com>: On Fri, 20 Jan 2023 18:01:38 +0100 you wrote: > TC mirred has a protection against excessive stack growth, but that > protection doesn't really guarantee the absence of recursion, nor > it guards against loops. Patch 1/2 rewords "recursion" to "nesting" to > make this more clear. > We can leverage on this existing mechanism to prevent TCP / SCTP from doing > soft lock-up in some specific scenarios that uses mirred egress->ingress: > patch 2 changes mirred so that the networking backlog is used for nested > mirred ingress actions. > > [...] Here is the summary with links: - [net-next,1/2] net/sched: act_mirred: better wording on protection against excessive stack growth https://git.kernel.org/netdev/net-next/c/78dcdffe0418 - [net-next,2/2] act_mirred: use the backlog for nested calls to mirred ingress https://git.kernel.org/netdev/net-next/c/ca22da2fbd69 You are awesome, thank you!
TC mirred has a protection against excessive stack growth, but that protection doesn't really guarantee the absence of recursion, nor it guards against loops. Patch 1/2 rewords "recursion" to "nesting" to make this more clear. We can leverage on this existing mechanism to prevent TCP / SCTP from doing soft lock-up in some specific scenarios that uses mirred egress->ingress: patch 2 changes mirred so that the networking backlog is used for nested mirred ingress actions. Davide Caratti (2): net/sched: act_mirred: better wording on protection against excessive stack growth act_mirred: use the backlog for nested calls to mirred ingress net/sched/act_mirred.c | 23 ++++++--- .../selftests/net/forwarding/tc_actions.sh | 49 ++++++++++++++++++- 2 files changed, 63 insertions(+), 9 deletions(-)