New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 620783 link

Starred by 2 users
Status: Verified
Owner:
█ dtor@chromium.org
Last visit > 30 days ago
Closed: Jun 2016
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 615221
issue 615222



Sign in to add a comment

Test failures due to new suid/sgid binaries seen if ARC++ is enabled

Project Member Reported by groeck@chromium.org, Jun 16 2016 
The following permission problems are reported by autotest if ARC++ is enabled.

New suid binaries: /opt/google/containers/android/rootfs/root/system/xbin/su, /opt/google/containers/android/rootfs/root/system/xbin/librank, /opt/google/containers/android/rootfs/root/system/xbin/procrank, /opt/google/containers/android/rootfs/root/system/xbin/procmem.

Also see:
https://buganizer.corp.google.com/u/0/issues/29003204

Comment 1 by groeck@chromium.org, Jun 16 2016

Blocking: 615222
Summary: File permission errors (new suid/sgid binaries) seen if ARC++ is enabled (was: File permission errors (new suid binaries) seen if ARC++ is enabled)
Also:

FAIL: New sgid binaries:
/opt/google/containers/android/rootfs/root/system/xbin/librank,
/opt/google/containers/android/rootfs/root/system/xbin/procrank,
/opt/google/containers/android/rootfs/root/system/xbin/procmem

Comment 2 by groeck@chromium.org, Jun 16 2016

Summary: Test failures due to new suid/sgid binaries seen if ARC++ is enabled (was: File permission errors (new suid/sgid binaries) seen if ARC++ is enabled)

Comment 3 by dtor@chromium.org, Jun 16 2016

Labels: -OS-Linux -OS-Android OS-Chrome
Status: Fixed (was: Assigned)
Now that we no longer package userdebug release these files are gone from the container image.

Comment 4 by groeck@chromium.org, Jun 17 2016

Status: Verified (was: Fixed)
►

Sign in to add a comment