summaryrefslogtreecommitdiff
path: root/libutils/ProcessCallStack_fuzz.cpp
diff options
context:
space:
mode:
authorBowgo Tsai <bowgotsai@google.com>2019-05-17 15:40:18 +0800
committerBowgo Tsai <bowgotsai@google.com>2019-05-22 16:15:44 +0800
commit3182ea132e917b197149fee74a7eeba5b6b5125d (patch)
tree774392bf43efd5950855b36e7e2bbb098907000f /libutils/ProcessCallStack_fuzz.cpp
parent9b77c0ba32b35e71ef0dc918b23fc7a438044c1f (diff)
Moving /odm/build.prop to /odm/etc/buid.prop
In device root directory, we have the following symlinks: - /odm/app -> /vendor/odm/app - /odm/bin -> /vendor/odm/bin - /odm/etc -> /vendor/odm/etc ... This allows the Generic System Image (GSI) to be used on both devices: 1) Has a physical odm partition, where those symlink will be hidden when /odm is used as the mount point 2) Has no physical odm partition and fallback to /vendor/odm/. We can't just have the symlink /odm -> /vendor/odm, because the former devices won't have /vendor/odm directory, which leads to mount failure when the mount point /odm is resolved to /vendor/odm. The existing /vendor/odm/build.prop won't be loaded in the latter devices, because there is no symlink - /odm/build.prop -> /vendor/odm/build.prop. Note that init blocks reading through direct symlinks (O_NOFOLLOW) so the above symlink won't work either. This CL moves the odm build.prop to /odm/etc/build.prop for init to load it (symlinks in earlier components of the path will still be followed by O_NOFOLLOW). Bug: 132128501 Test: boot a device and checks /odm/etc/build.prop is loaded Change-Id: I0733c277baa67c549bb45599abb70aba13fbdbcf Merged-In: I0733c277baa67c549bb45599abb70aba13fbdbcf (cherry picked from commit c49655b2a48eca2ab751b853a9a4692f322cafa2)
Diffstat (limited to 'libutils/ProcessCallStack_fuzz.cpp')
0 files changed, 0 insertions, 0 deletions