[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210114070904.9981-1-jasowang@redhat.com>
Date: Thu, 14 Jan 2021 15:09:04 +0800
From: Jason Wang <jasowang@...hat.com>
To: mst@...hat.com, jasowang@...hat.com,
virtualization@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org
Cc: elic@...dia.com
Subject: [PATCH V2] mlx5: vdpa: fix possible uninitialized var
When compiling with -Werror=maybe-uninitialized, gcc may complains the
possible uninitialized umem. Since the callers won't pass value other
than 1 to 3, making 3 as default to fix the compiler warning.
Signed-off-by: Jason Wang <jasowang@...hat.com>
---
drivers/vdpa/mlx5/net/mlx5_vnet.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/vdpa/mlx5/net/mlx5_vnet.c b/drivers/vdpa/mlx5/net/mlx5_vnet.c
index f1d54814db97..07ccc61cd6f6 100644
--- a/drivers/vdpa/mlx5/net/mlx5_vnet.c
+++ b/drivers/vdpa/mlx5/net/mlx5_vnet.c
@@ -703,7 +703,7 @@ static void umem_destroy(struct mlx5_vdpa_net *ndev, struct mlx5_vdpa_virtqueue
case 2:
umem = &mvq->umem2;
break;
- case 3:
+ default:
umem = &mvq->umem3;
break;
}
--
2.25.1
Powered by blists - more mailing lists