applied: [PATCH manager v4 0/2] fix #6735: api: pci: allow mdevscan access via mapping permissions

[Thomas Lamprecht <t.lamprecht@proxmox.com>]

On Fri, 04 Sep 2026 11:44:52 +0200, Elias Huhsovitz wrote:
> This series allows users who have been granted Mapping.Use
> (or Mapping.Modify / Mapping.Audit) on a specific PCI mapping to list
> the mediated device (mdev) types for that mapping without requiring
> global Sys.Audit or Sys.Modify privileges on the entire cluster.
> 
> In multi‑team environments where access is compartmentalized via
> resource pools and PCI mappings, the previous requirement forced
> administrators to grant overly broad permissions for GPU usage.
> By checking mapping‑specific permissions when a mapping name is
> supplied, the patch enables non‑administrative users to select and use
> vGPU types for their assigned hardware.
> 
> [...]

Applied the first one, but dropped the constant, thanks!

more rationale: IMO that constant name was not ideal as it was rather generic
and even if that was addressed we still had repetition here by listing the
privs explicit in the description, which can go out of sync much easier that
way. Also, not a common pattern we use in our code base and IMO also just not
gaining one that much to add such indirection variables/constants.

[1/2] fix #6735: api: pci: allow mdevscan access via mapping permissions
      https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=58350116c198b838dfb50739e886bc92bcc751c3
[2/2] api: pci: utilize constant perm variable for pci_scan
      DROPPED