I don't think those are on your commands as the target context is init_shell and not su or shell.
Are you running aosp, the nsa code base or is this on something custom? Bill Tomas <[email protected]> wrote: Hi, I am getting sigchild denials below, that I cannot figure out. They only appear when using su access. Eg. when root-explorer or other utility list files or processes. Not sure if I understand the message correct; who is actually sending the sigchld and why is it denied? I am unable to find logs from other devices showing samme denial. Using same BusyBox as many other. Thanks Tomas { sigchld } for pid=5594 comm="sh" scontext=u:r:zygote:s0 tcontext=u:r:init_shell:s0 tclass=process # adb shell su 0 ps -Z | grep sh u:r:adbd:s0 shell 177 1 /sbin/adbd u:r:shell:s0 shell 5064 177 /system/bin/sh u:r:init_shell:s0 root 5262 5260 sh u:r:init_shell:s0 root 5496 5262 sh u:r:init_shell:s0 root 5594 5593 sh -rwxr-xr-x root shell u:object_r:shell_exec:s0 mksh lrwxrwxrwx root root u:object_r:shell_exec:s0 sh -> mksh ------ BusyBox: ------ root@android:/ # ps -Z | grep su u:r:init:s0 root 176 1 /system/xbin/su u:r:su:s0 root 5254 5064 su u:r:su:s0 root 5255 5254 su u:r:init:s0 root 5258 1 /system/xbin/su u:r:init:s0 root 5260 5258 /system/xbin/su u:r:untrusted_app:s0 u0_a61 5589 1950 /system/bin/su u:r:untrusted_app:s0 u0_a61 5590 5589 /system/bin/su u:r:init:s0 root 5592 1 /system/xbin/su u:r:init:s0 root 5593 5592 /system/xbin/su u:r:su:s0 root 6598 6297 su u:r:su:s0 root 6599 6598 su u:r:init:s0 root 6601 1 /system/xbin/su u:r:init:s0 root 6603 6601 /system/xbin/su # adb shell su 0 ls -Z /system/bin/ | grep su lrwxrwxrwx root root u:object_r:system_file:s0 su -> ../xbin/su # adb shell su 0 ls -Z /system/xbin/| grep su -rwsr-sr-x root root u:object_r:su_exec:s0 su _______________________________________________ Seandroid-list mailing list [email protected] To unsubscribe, send email to [email protected]. To get help, send an email containing "help" to [email protected].
