File permission errors seen if ARC++ is enabled |
||
Issue descriptionThe following file permission errors are reported by autotest if ARC++ is enabled. ERROR|platform_FilePerms:0273| No expectations entry for "/sys/fs/selinux" ERROR|platform_FilePerms:0293| [/var/log/mount_options.log] "/sys" is missing options "set(['noexec', 'nosuid', 'nodev'])" ERROR|platform_FilePerms:0273| No expectations entry for "/opt/google/containers/android/rootfs/root/vendor" ERROR|platform_FilePerms:0273| No expectations entry for "/opt/google/containers/android/rootfs/root" ERROR|platform_FilePerms:0273| No expectations entry for "/sys/fs/selinux" ERROR|platform_FilePerms:0293| [/etc/mtab] "/sys" is missing options "set(['noexec', 'nosuid', 'nodev'])" Also see: https://buganizer.corp.google.com/u/0/issues/25024410 https://buganizer.corp.google.com/u/0/issues/29003204
,
Jun 21 2016
,
Jul 18 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/eb01a716b480188c2193525fc51b3e8dd20b2202 commit eb01a716b480188c2193525fc51b3e8dd20b2202 Author: Nicolas Norvez <norvez@google.com> Date: Tue Jul 12 16:54:03 2016 platform_FilePerms: Don't enforce 'noexec' on container Do not enforce 'noexec' on /opt/google/containers/android/rootfs/root and /opt/google/containers/android/rootfs/root/vendor because they are remounted as 'exec' after a user logs in (see CL:351221), which is what happens when the test is run as part of a test suite, e.g. the smoke suite BUG= chromium:620788 TEST=Ran smoke test suite on cyan-cheets and VM Change-Id: I3c61a2baf759de69a7cb37aa2a4e7a6ac824ac32 Reviewed-on: https://chromium-review.googlesource.com/361310 Commit-Ready: Nicolas Norvez <norvez@chromium.org> Tested-by: Nicolas Norvez <norvez@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org> [modify] https://crrev.com/eb01a716b480188c2193525fc51b3e8dd20b2202/client/site_tests/platform_FilePerms/platform_FilePerms.py
,
Jul 18 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/eb01a716b480188c2193525fc51b3e8dd20b2202 commit eb01a716b480188c2193525fc51b3e8dd20b2202 Author: Nicolas Norvez <norvez@google.com> Date: Tue Jul 12 16:54:03 2016 platform_FilePerms: Don't enforce 'noexec' on container Do not enforce 'noexec' on /opt/google/containers/android/rootfs/root and /opt/google/containers/android/rootfs/root/vendor because they are remounted as 'exec' after a user logs in (see CL:351221), which is what happens when the test is run as part of a test suite, e.g. the smoke suite BUG= chromium:620788 TEST=Ran smoke test suite on cyan-cheets and VM Change-Id: I3c61a2baf759de69a7cb37aa2a4e7a6ac824ac32 Reviewed-on: https://chromium-review.googlesource.com/361310 Commit-Ready: Nicolas Norvez <norvez@chromium.org> Tested-by: Nicolas Norvez <norvez@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org> [modify] https://crrev.com/eb01a716b480188c2193525fc51b3e8dd20b2202/client/site_tests/platform_FilePerms/platform_FilePerms.py |
||
►
Sign in to add a comment |
||
Comment 1 by dtor@chromium.org
, Jun 17 2016Status: Fixed (was: Assigned)