mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-06 20:03:33 -04:00
vfio-pci: Mask cap zero
[ Upstream commit bc138db1b96264b9c1779cf18d5a3b186aa90066 ] The PCI Code and ID Assignment Specification changed capability ID 0 from reserved to a NULL capability in the v1.1 revision. The NULL capability is defined to include only the 16-bit capability header, ie. only the ID and next pointer. Unfortunately vfio-pci creates a map of config space, where ID 0 is used to reserve the standard type 0 header. Finding an actual capability with this ID therefore results in a bogus range marked in that map and conflicts with subsequent capabilities. As this seems to be a dummy capability anyway and we already support dropping capabilities, let's hide this one rather than delving into the potentially subtle dependencies within our map. Seen on an NVIDIA Tesla T4. Reviewed-by: Cornelia Huck <cohuck@redhat.com> Signed-off-by: Alex Williamson <alex.williamson@redhat.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:
parent
f5e28a0824
commit
8a67dae365
1 changed files with 6 additions and 1 deletions
|
|
@ -1460,7 +1460,12 @@ static int vfio_cap_init(struct vfio_pci_device *vdev)
|
|||
if (ret)
|
||||
return ret;
|
||||
|
||||
if (cap <= PCI_CAP_ID_MAX) {
|
||||
/*
|
||||
* ID 0 is a NULL capability, conflicting with our fake
|
||||
* PCI_CAP_ID_BASIC. As it has no content, consider it
|
||||
* hidden for now.
|
||||
*/
|
||||
if (cap && cap <= PCI_CAP_ID_MAX) {
|
||||
len = pci_cap_length[cap];
|
||||
if (len == 0xFF) { /* Variable length */
|
||||
len = vfio_cap_len(vdev, cap, pos);
|
||||
|
|
|
|||
Loading…
Reference in a new issue