diff options
| author |   Eli Cohen <elic@nvidia.com> | 2022-01-11 20:33:59 +0200 |
|---|---|---|
| committer |   Michael S. Tsirkin <mst@redhat.com> | 2022-01-14 18:50:54 -0500 |
| commit | f8ae3a489b21b05c39a0a1a7734f2a0188852177 (patch) | |
| tree | 0f35a899de9f653482a351e3d4157e9a35d22660 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | vdpa: Protect vdpa reset with cf_mutex (diff) | |
| download | wireguard-linux-f8ae3a489b21b05c39a0a1a7734f2a0188852177.tar.xz wireguard-linux-f8ae3a489b21b05c39a0a1a7734f2a0188852177.zip | |
vdpa/mlx5: Fix is_index_valid() to refer to features
Make sure the decision whether an index received through a callback is
valid or not consults the negotiated features.
The motivation for this was due to a case encountered where I shut down
the VM. After the reset operation was called features were already
clear, I got get_vq_state() call which caused out array bounds
access since is_index_valid() reported the index value.
So this is more of not hit a bug since the call shouldn't have been made
first place.
Signed-off-by: Eli Cohen <elic@nvidia.com>
Link: https://lore.kernel.org/r/20220111183400.38418-4-elic@nvidia.com
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Si-Wei Liu<si-wei.liu@oracle.com>
Acked-by: Jason Wang <jasowang@redhat.com>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions