[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y87CWGgHk8f0EWfA@t14s.localdomain>
Date: Mon, 23 Jan 2023 14:22:32 -0300
From: Marcelo Ricardo Leitner <marcelo.leitner@...il.com>
To: Davide Caratti <dcaratti@...hat.com>
Cc: jhs@...atatu.com, jiri@...nulli.us, lucien.xin@...il.com,
netdev@...r.kernel.org, pabeni@...hat.com, wizhao@...hat.com,
xiyou.wangcong@...il.com
Subject: Re: [PATCH net-next 1/2] net/sched: act_mirred: better wording on
protection against excessive stack growth
On Fri, Jan 20, 2023 at 06:01:39PM +0100, Davide Caratti wrote:
> with commit e2ca070f89ec ("net: sched: protect against stack overflow in
> TC act_mirred"), act_mirred protected itself against excessive stack growth
> using per_cpu counter of nested calls to tcf_mirred_act(), and capping it
> to MIRRED_RECURSION_LIMIT. However, such protection does not detect
> recursion/loops in case the packet is enqueued to the backlog (for example,
> when the mirred target device has RPS or skb timestamping enabled). Change
> the wording from "recursion" to "nesting" to make it more clear to readers.
>
> CC: Jamal Hadi Salim <jhs@...atatu.com>
> Signed-off-by: Davide Caratti <dcaratti@...hat.com>
Reviewed-by: Marcelo Ricardo Leitner <marcelo.leitner@...il.com>
Powered by blists - more mailing lists