Create Task
Maniphest T4955

[bullhead] Permissions for android device nodes are wrong inside container
Closed, ResolvedPublic
Actions

Description

Somehow permissions for android device nodes are wrong inside the container.

Important ones are,

root@bullhead:/ # ls -l /dev/kgsl-3d0
crw-rw-rw- system   system   238,   0 1970-02-18 21:49 kgsl-3d0
root@bullhead:/ # ls -l /dev/ion      
crw-rw-r-- system   system    10,  95 1970-02-18 21:48 ion

Those seems not to have 600 permissions inside container somehow and needs to be fixed.

A simple workaround for now is,

phablet@ubuntu-phablet:~$ cat /etc/udev/rules.d/55-android.rules
KERNEL=="kgsl-3d0" MODE="0666"
KERNEL=="ion" MODE="0666"

But this shows bigger issue and needs to be fixed first.

Related Objects
Search...

bshah created this task.Dec 22 2016, 3:10 AM
bshah updated the task description. (Show Details)Dec 22 2016, 3:31 AM
bshah closed this task as Resolved.Jan 7 2017, 3:30 PM

This was one hell of issue with one-liner stupid mistake to fix..

Somehow, for some reason I enabled DEVTMPFS_MOUNT option in the kernel config, which makes it to mout /dev with devtmpfs automatically

config DEVTMPFS_MOUNT                                                     
    bool "Automount devtmpfs at /dev, after the kernel mounted the rootfs"
    depends on DEVTMPFS                                                   
    help                                                                  
      This will instruct the kernel to automatically mount the            
      devtmpfs filesystem at /dev, directly after the kernel has          
      mounted the root filesystem. The behavior can be overridden         
      with the commandline parameter: devtmpfs.mount=0|1.                 
      This option does not affect initramfs based booting, here           
      the devtmpfs filesystem always needs to be mounted manually         
      after the roots is mounted.                                         
      With this option enabled, it allows to bring up a system in         
      rescue mode with init=/bin/sh, even when the /dev directory         
      on the rootfs is completely empty.

This resulted in problems as android doesn't use devtmpfs but mounts empty tmpfs at /dev.

Now fixed.

bshah reopened this task as Open.Jan 18 2017, 3:03 AM

Um. this doesn't got fixed with this.. reopening.

bshah closed this task as Resolved.Nov 26 2017, 7:42 AM

Resolved with Halium