net/mlx5: panic when destroying a queue in use
authorNélio Laranjeiro <nelio.laranjeiro@6wind.com>
Tue, 11 Apr 2017 15:21:52 +0000 (17:21 +0200)
committerFerruh Yigit <ferruh.yigit@intel.com>
Wed, 19 Apr 2017 13:37:37 +0000 (15:37 +0200)
commit3b57c21ef9d0c434968798338292d14ab61290d4
tree96b773fbb7a598d2d8c4d4bb4a94eb1b1a05dfd6
parentc5b723ec8e3afd5cb26d9692fd87fc58aed0d607
net/mlx5: panic when destroying a queue in use

Since the queue release API does not allow failures (return value is void)
and the flow API does not allow a queue to be released as long as a flow
rule depends on it, the only rational decision to avoid undefined behavior
is to panic in this situation.

Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
drivers/net/mlx5/mlx5.h
drivers/net/mlx5/mlx5_flow.c
drivers/net/mlx5/mlx5_rxq.c