[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190225.101829.46711684456598689.davem@davemloft.net>
Date: Mon, 25 Feb 2019 10:18:29 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: vladbu@...lanox.com
Cc: netdev@...r.kernel.org, jhs@...atatu.com, xiyou.wangcong@...il.com,
jiri@...nulli.us
Subject: Re: [PATCH net-next] net: sched: set dedicated tcf_walker flag
when tp is empty
From: Vlad Buslov <vladbu@...lanox.com>
Date: Mon, 25 Feb 2019 17:38:31 +0200
> Using tcf_walker->stop flag to determine when tcf_walker->fn() was called
> at least once is unreliable. Some classifiers set 'stop' flag on error
> before calling walker callback, other classifiers used to call it with NULL
> filter pointer when empty. In order to prevent further regressions, extend
> tcf_walker structure with dedicated 'nonempty' flag. Set this flag in
> tcf_walker->fn() implementation that is used to check if classifier has
> filters configured.
>
> Fixes: 8b64678e0af8 ("net: sched: refactor tp insert/delete for concurrent execution")
> Signed-off-by: Vlad Buslov <vladbu@...lanox.com>
> Suggested-by: Cong Wang <xiyou.wangcong@...il.com>
Applied, thanks.
Powered by blists - more mailing lists