[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210108082443.5609-1-jasowang@redhat.com>
Date: Fri, 8 Jan 2021 16:24:43 +0800
From: Jason Wang <jasowang@...hat.com>
To: mst@...hat.com, jasowang@...hat.com
Cc: elic@...dia.com, virtualization@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org
Subject: [PATCH] mlx5: vdpa: fix possible uninitialized var
Upstream: posted
When compiling with -Werror=maybe-uninitialized, gcc may complains the
possible uninitialized umem. Fix that.
Signed-off-by: Jason Wang <jasowang@...hat.com>
---
drivers/vdpa/mlx5/net/mlx5_vnet.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/vdpa/mlx5/net/mlx5_vnet.c b/drivers/vdpa/mlx5/net/mlx5_vnet.c
index f1d54814db97..a6ad83d8d8e2 100644
--- a/drivers/vdpa/mlx5/net/mlx5_vnet.c
+++ b/drivers/vdpa/mlx5/net/mlx5_vnet.c
@@ -706,6 +706,9 @@ static void umem_destroy(struct mlx5_vdpa_net *ndev, struct mlx5_vdpa_virtqueue
case 3:
umem = &mvq->umem3;
break;
+ default:
+ WARN(1, "unsupported umem num %d\n", num);
+ return;
}
MLX5_SET(destroy_umem_in, in, opcode, MLX5_CMD_OP_DESTROY_UMEM);
--
2.25.1
Powered by blists - more mailing lists