Public bug reported:

This bug targets the linux-amd-embedded kernel (Ubuntu 26.04 Resolute,
7.0, amd64). linux-amd-embedded is not yet available in the archive, so
the bug is filed against the linux package for now.

[Impact]
The vcn_v4_0_5 code in amdgpu handles both VCN 4.0.5 and VCN 4.0.6, but secure 
submission on the unified ring is only enabled at runtime for VCN 4.0.5. On VCN 
4.0.6, secure IBs are rejected, so hardware decoding of protected content fails.

[Fix]
 * Backport from mainline (v7.3-rc1):
   - 44d1cb67f6c4 ("drm/amdgpu/vcn4.0.5: enable secure submission on unified 
ring")

[Test Plan]
 * Build the linux-amd-embedded kernel for all flavours.
 * Boot the kernel in an LXD VM and load the amdgpu module.

[Where problems could occur]
The change only affects the VCN unified ring of the vcn_v4_0_5 code. Secure 
submission is now also allowed on VCN 4.0.6, and nothing changes on VCN 4.0.5. 
A regression could cause problems with protected video decoding on these VCN 
versions. Non-secure decode is not affected.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: linux (Ubuntu Resolute)
     Importance: High
     Assignee: Krystian Kaniewski (kkaniewski)
         Status: Confirmed

** Also affects: linux (Ubuntu Resolute)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Resolute)
     Assignee: (unassigned) => Krystian Kaniewski (kkaniewski)

** Changed in: linux (Ubuntu Resolute)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Resolute)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2174710

Title:
  linux-amd-embedded: Enable secure submission on the VCN 4.0.6 unified
  ring

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174710/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to