** Description changed:

+ [Impact]
+ 
+ The incorrect permissions on these devices mean the regular console user
+ cannot access various videocore services. An example of a side-effect of
+ this is that camera usage (via the new libcamera mechanism) requires
+ root access. Likewise, usage of the GPU (under the KMS system) for H.264
+ decoding (via v4l2m2m) likewise requires root access.
+ 
+ [Test Plan]
+ 
+ * Flash a focal image to a fresh SD card and boot it
+ * ls -l /dev/vc* /dev/vid*
+ * Note that /dev/vcio, /dev/vcsm-cma, and ??? have incorrect permissions 
(specifically, their ownership is not root:video and/or their mode is not 0664)
+ * sudo add-apt-repository ppa:waveform/userland
+ * sudo apt install libraspberrypi0
+ * sudo reboot
+ * ls -l /dev/vc* /dev/vid*
+ * Note that /dev/vcio, /dev/vcsm-cma, and ??? now have correct permissions 
(root:video ownership, and mode 0664)
+ 
+ [Regression Potential]
+ 
+ Only the permission changes are being backported, not a fully updated
+ userland. Nonetheless, existing functionality from userland should be
+ re-tested, in particular the legacy camera stack, with the following
+ procedure:
+ 
+ * Attach a raspberry pi camera module to the board
+ * Add "start_x=1" and "gpu_mem=128" to /boot/firmware/config.txt
+ * sudo reboot
+ * raspistill -o test.jpg
+ * Confirm that test.jpg contains a valid picture
+ 
+ The "tvservice" binary *may* be tested too, but is known to be
+ inoperable under the arm64 architecture (see LP: #1944541). It is also
+ worth noting that the test plan above only looks at the permissions as
+ libcamera is not *currently* expected to operate on Focal.
+ 
+ [Original Description]
+ 
  The /dev/vcio can have the wrong permissions due to a change in the
  kernel. As reported in https://github.com/raspberrypi/linux/pull/4624
  (which I missed entirely, sorry pelwell!) we'll need a change in the
  udev rules to ensure the correct permissions are set.

** Description changed:

  [Impact]
  
  The incorrect permissions on these devices mean the regular console user
  cannot access various videocore services. An example of a side-effect of
  this is that camera usage (via the new libcamera mechanism) requires
  root access. Likewise, usage of the GPU (under the KMS system) for H.264
  decoding (via v4l2m2m) likewise requires root access.
  
  [Test Plan]
  
- * Flash a focal image to a fresh SD card and boot it
+ * Flash the appropriate version to a fresh SD card and boot it
  * ls -l /dev/vc* /dev/vid*
  * Note that /dev/vcio, /dev/vcsm-cma, and ??? have incorrect permissions 
(specifically, their ownership is not root:video and/or their mode is not 0664)
  * sudo add-apt-repository ppa:waveform/userland
  * sudo apt install libraspberrypi0
  * sudo reboot
  * ls -l /dev/vc* /dev/vid*
  * Note that /dev/vcio, /dev/vcsm-cma, and ??? now have correct permissions 
(root:video ownership, and mode 0664)
  
  [Regression Potential]
  
  Only the permission changes are being backported, not a fully updated
  userland. Nonetheless, existing functionality from userland should be
  re-tested, in particular the legacy camera stack, with the following
  procedure:
  
  * Attach a raspberry pi camera module to the board
  * Add "start_x=1" and "gpu_mem=128" to /boot/firmware/config.txt
  * sudo reboot
  * raspistill -o test.jpg
  * Confirm that test.jpg contains a valid picture
  
  The "tvservice" binary *may* be tested too, but is known to be
  inoperable under the arm64 architecture (see LP: #1944541). It is also
  worth noting that the test plan above only looks at the permissions as
  libcamera is not *currently* expected to operate on Focal.
  
+ Tests should be carried out on all supported boards (Zero 2, 2B, 3B,
+ 3A+, 3B+, 4B) under both armhf and arm64 architectures (within the
+ caveats noted above about the arm64 architecture).
+ 
  [Original Description]
  
  The /dev/vcio can have the wrong permissions due to a change in the
  kernel. As reported in https://github.com/raspberrypi/linux/pull/4624
  (which I missed entirely, sorry pelwell!) we'll need a change in the
  udev rules to ensure the correct permissions are set.

** Changed in: raspberrypi-userland (Ubuntu Impish)
     Assignee: (unassigned) => Dave Jones (waveform)

** Changed in: raspberrypi-userland (Ubuntu Focal)
     Assignee: (unassigned) => Dave Jones (waveform)

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

Title:
  [SRU] Wrong permissions on vcio

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/raspberrypi-userland/+bug/1958563/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to