From: Davide Caratti <dcaratti@redhat•com>
To: jhs@mojatatu•com
Cc: jiri@resnulli•us, lucien.xin@gmail•com,
marcelo.leitner@gmail•com, netdev@vger•kernel.org,
pabeni@redhat•com, wizhao@redhat•com, xiyou.wangcong@gmail•com
Subject: [PATCH net-next 0/2] net/sched: use the backlog for nested mirred ingress
Date: Fri, 20 Jan 2023 18:01:38 +0100 [thread overview]
Message-ID: <cover.1674233458.git.dcaratti@redhat.com> (raw)
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(-)
--
2.38.1
next reply other threads:[~2023-01-20 17:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 17:01 Davide Caratti [this message]
2023-01-20 17:01 ` [PATCH net-next 1/2] net/sched: act_mirred: better wording on protection against excessive stack growth Davide Caratti
2023-01-23 17:22 ` Marcelo Ricardo Leitner
2023-01-23 19:40 ` Jamal Hadi Salim
2023-01-20 17:01 ` [PATCH net-next 2/2] act_mirred: use the backlog for nested calls to mirred ingress Davide Caratti
2023-01-23 17:22 ` Marcelo Ricardo Leitner
2023-01-23 19:41 ` Jamal Hadi Salim
2023-12-04 20:24 ` Mirred broken WAS(Re: " Jamal Hadi Salim
2023-12-05 10:54 ` Davide Caratti
2023-12-05 15:12 ` Jamal Hadi Salim
2023-12-07 14:10 ` Jamal Hadi Salim
2023-12-11 13:07 ` Davide Caratti
2023-12-11 15:50 ` Jamal Hadi Salim
2023-01-24 9:40 ` [PATCH net-next 0/2] net/sched: use the backlog for nested " patchwork-bot+netdevbpf
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=cover.1674233458.git.dcaratti@redhat.com \
--to=dcaratti@redhat$(echo .)com \
--cc=jhs@mojatatu$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=lucien.xin@gmail$(echo .)com \
--cc=marcelo.leitner@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=wizhao@redhat$(echo .)com \
--cc=xiyou.wangcong@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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