[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180803.094517.666241811188161799.davem@davemloft.net>
Date: Fri, 03 Aug 2018 09:45:17 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: jiri@...nulli.us
Cc: netdev@...r.kernel.org, jhs@...atatu.com, xiyou.wangcong@...il.com,
jakub.kicinski@...ronome.com, idosch@...lanox.com,
mlxsw@...lanox.com
Subject: Re: [patch net-next] net: sched: fix flush on non-existing chain
From: Jiri Pirko <jiri@...nulli.us>
Date: Fri, 3 Aug 2018 11:08:47 +0200
> From: Jiri Pirko <jiri@...lanox.com>
>
> User was able to perform filter flush on chain 0 even if it didn't have
> any filters in it. With the patch that avoided implicit chain 0
> creation, this changed. So in case user wants filter flush on chain
> which does not exist, just return success. There's no reason for non-0
> chains to behave differently than chain 0, so do the same for them.
>
> Reported-by: Ido Schimmel <idosch@...lanox.com>
> Fixes: f71e0ca4db18 ("net: sched: Avoid implicit chain 0 creation")
> Signed-off-by: Jiri Pirko <jiri@...lanox.com>
Applied.
Powered by blists - more mailing lists