6.7 in noble has this

** Changed in: linux (Ubuntu Noble)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2047461

Title:
  drm: Update file owner during use

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Fix Released
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  Our testing tools need to check the app runs on which GPU, and now it only 
shows the processes as Xorg or XWayland

      $ cat /sys/kernel/debug/dri/0/clients
                   command   pid dev master a   uid      magic
                      Xorg  2344   0   y    y     0          0
                      Xorg  2344   0   n    y     0          2
                      Xorg  2344   0   n    y     0          3
                      Xorg  2344   0   n    y     0          4

  [Fix]
  The commit from v6.7-rc1 fixes the issue

      $ cat /sys/kernel/debug/dri/0/clients
                   command  tgid dev master a   uid      magic
                      Xorg   830   0   y    y     0          0
             xfce4-session   880   0   n    y     0          1
                     xfwm4   943   0   n    y     0          2
                 neverball  1095   0   n    y     0          3

  
  [Test case]
  1. check processes by 'cat /sys/kernel/debug/dri/0/clients'
  2. runs glxgears(specify the GPU if needed)
  3. check the precesses again and there should be a 'glxgears' process 

  [Where problems could occur]
  This commit added some protections on read/write and only changes the 
process' pid, the worst case is that the process got the wrong pid as its owner.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to