platform_system_core/rootdir/etc/ld.config.txt

121 lines
6.6 KiB
Plaintext
Raw Normal View History

# Copyright (C) 2017 The Android Open Source Project
#
# Bionic loader config file.
#
Configure ld.config.txt for SP-HALs Now, framework process (any process that is executing /system/bin/* or /system/xbin/*) are started with three namespaces; default, sphal and vndk. default namespace is the namespace that is responsible for loading libs from /system/lib. It can't load libs from other places such as /vendor/lib. (However, we temporarily open the path since we haven't finished the system partition cleanup, but will do eventually). sphal namespace is the namespace where SP-HAL (Same-process HAL) is loaded. SP-HAL are the only vendor libraries that are allowed to be loaded inside framework processes. libEGL_<chipset>.so and android.hardware.graphics.mapper@2.0-impl.so, etc are SP-HALs. When framework needs to load those SP-HALs, it explicitly loads it from this namespace using android_get_exported_namespace() and android_dlopen_ext(). vndk namespace is the namespace for loading vndk-sp (Vendor-NDK for Same-Process) libs, which is a small set of framework libraries that SP-HALs can link against. These libraries are compiled for the same version of Android that the vendor partition is compiled against. SP-HALs can not use libraries other than vndk-sp and ndk libs. Membership to vndk-sp and ndk are strictly closed. Note that in a system, there are two copies of vndk-sp libs. One at /system/lib and the other at /vendor/lib/vndk-sp. As a result, there can be two instances of a same library in a process. Also adds ld.config.legacy.txt which is used on non-Treble devices where PRODUCT_FULL_TREBLE is not set to true. Note, this split can be cleaned up further after b/37139976 is solved. Bug: 34407260 Test: git diff HEAD:rootdir/etc/ld.config.legacy.txt HEAD^:rootdir/etc/ld.config.txt => 0 Test: sailfish boots (because BOARD_VNDK_VERSION is not set to 'current') Change-Id: I8331d94edc38f22c4f8abc66cdf2050af9d0605b
2017-04-05 13:24:14 +08:00
# Don't change the order here.
dir.system = /system/bin/
dir.system = /system/xbin/
dir.vendor = /vendor/bin/
Configure ld.config.txt for SP-HALs Now, framework process (any process that is executing /system/bin/* or /system/xbin/*) are started with three namespaces; default, sphal and vndk. default namespace is the namespace that is responsible for loading libs from /system/lib. It can't load libs from other places such as /vendor/lib. (However, we temporarily open the path since we haven't finished the system partition cleanup, but will do eventually). sphal namespace is the namespace where SP-HAL (Same-process HAL) is loaded. SP-HAL are the only vendor libraries that are allowed to be loaded inside framework processes. libEGL_<chipset>.so and android.hardware.graphics.mapper@2.0-impl.so, etc are SP-HALs. When framework needs to load those SP-HALs, it explicitly loads it from this namespace using android_get_exported_namespace() and android_dlopen_ext(). vndk namespace is the namespace for loading vndk-sp (Vendor-NDK for Same-Process) libs, which is a small set of framework libraries that SP-HALs can link against. These libraries are compiled for the same version of Android that the vendor partition is compiled against. SP-HALs can not use libraries other than vndk-sp and ndk libs. Membership to vndk-sp and ndk are strictly closed. Note that in a system, there are two copies of vndk-sp libs. One at /system/lib and the other at /vendor/lib/vndk-sp. As a result, there can be two instances of a same library in a process. Also adds ld.config.legacy.txt which is used on non-Treble devices where PRODUCT_FULL_TREBLE is not set to true. Note, this split can be cleaned up further after b/37139976 is solved. Bug: 34407260 Test: git diff HEAD:rootdir/etc/ld.config.legacy.txt HEAD^:rootdir/etc/ld.config.txt => 0 Test: sailfish boots (because BOARD_VNDK_VERSION is not set to 'current') Change-Id: I8331d94edc38f22c4f8abc66cdf2050af9d0605b
2017-04-05 13:24:14 +08:00
[system]
additional.namespaces = sphal,vndk,rs
Configure ld.config.txt for SP-HALs Now, framework process (any process that is executing /system/bin/* or /system/xbin/*) are started with three namespaces; default, sphal and vndk. default namespace is the namespace that is responsible for loading libs from /system/lib. It can't load libs from other places such as /vendor/lib. (However, we temporarily open the path since we haven't finished the system partition cleanup, but will do eventually). sphal namespace is the namespace where SP-HAL (Same-process HAL) is loaded. SP-HAL are the only vendor libraries that are allowed to be loaded inside framework processes. libEGL_<chipset>.so and android.hardware.graphics.mapper@2.0-impl.so, etc are SP-HALs. When framework needs to load those SP-HALs, it explicitly loads it from this namespace using android_get_exported_namespace() and android_dlopen_ext(). vndk namespace is the namespace for loading vndk-sp (Vendor-NDK for Same-Process) libs, which is a small set of framework libraries that SP-HALs can link against. These libraries are compiled for the same version of Android that the vendor partition is compiled against. SP-HALs can not use libraries other than vndk-sp and ndk libs. Membership to vndk-sp and ndk are strictly closed. Note that in a system, there are two copies of vndk-sp libs. One at /system/lib and the other at /vendor/lib/vndk-sp. As a result, there can be two instances of a same library in a process. Also adds ld.config.legacy.txt which is used on non-Treble devices where PRODUCT_FULL_TREBLE is not set to true. Note, this split can be cleaned up further after b/37139976 is solved. Bug: 34407260 Test: git diff HEAD:rootdir/etc/ld.config.legacy.txt HEAD^:rootdir/etc/ld.config.txt => 0 Test: sailfish boots (because BOARD_VNDK_VERSION is not set to 'current') Change-Id: I8331d94edc38f22c4f8abc66cdf2050af9d0605b
2017-04-05 13:24:14 +08:00
###############################################################################
# "default" namespace
#
Configure ld.config.txt for SP-HALs Now, framework process (any process that is executing /system/bin/* or /system/xbin/*) are started with three namespaces; default, sphal and vndk. default namespace is the namespace that is responsible for loading libs from /system/lib. It can't load libs from other places such as /vendor/lib. (However, we temporarily open the path since we haven't finished the system partition cleanup, but will do eventually). sphal namespace is the namespace where SP-HAL (Same-process HAL) is loaded. SP-HAL are the only vendor libraries that are allowed to be loaded inside framework processes. libEGL_<chipset>.so and android.hardware.graphics.mapper@2.0-impl.so, etc are SP-HALs. When framework needs to load those SP-HALs, it explicitly loads it from this namespace using android_get_exported_namespace() and android_dlopen_ext(). vndk namespace is the namespace for loading vndk-sp (Vendor-NDK for Same-Process) libs, which is a small set of framework libraries that SP-HALs can link against. These libraries are compiled for the same version of Android that the vendor partition is compiled against. SP-HALs can not use libraries other than vndk-sp and ndk libs. Membership to vndk-sp and ndk are strictly closed. Note that in a system, there are two copies of vndk-sp libs. One at /system/lib and the other at /vendor/lib/vndk-sp. As a result, there can be two instances of a same library in a process. Also adds ld.config.legacy.txt which is used on non-Treble devices where PRODUCT_FULL_TREBLE is not set to true. Note, this split can be cleaned up further after b/37139976 is solved. Bug: 34407260 Test: git diff HEAD:rootdir/etc/ld.config.legacy.txt HEAD^:rootdir/etc/ld.config.txt => 0 Test: sailfish boots (because BOARD_VNDK_VERSION is not set to 'current') Change-Id: I8331d94edc38f22c4f8abc66cdf2050af9d0605b
2017-04-05 13:24:14 +08:00
# Framework-side code runs in this namespace. Anything from /vendor partition
# can't be loaded in this namespace.
###############################################################################
namespace.default.isolated = false
namespace.default.search.paths = /system/${LIB}:/vendor/${LIB}
namespace.default.permitted.paths = /system/${LIB}:/vendor/${LIB}
namespace.default.asan.search.paths = /data/asan/system/${LIB}:/system/${LIB}:/data/asan/vendor/${LIB}:/vendor/${LIB}
namespace.default.asan.permitted.paths = /data/asan/system/${LIB}:/system/${LIB}:/data/asan/vendor/${LIB}:/vendor/${LIB}
Configure ld.config.txt for SP-HALs Now, framework process (any process that is executing /system/bin/* or /system/xbin/*) are started with three namespaces; default, sphal and vndk. default namespace is the namespace that is responsible for loading libs from /system/lib. It can't load libs from other places such as /vendor/lib. (However, we temporarily open the path since we haven't finished the system partition cleanup, but will do eventually). sphal namespace is the namespace where SP-HAL (Same-process HAL) is loaded. SP-HAL are the only vendor libraries that are allowed to be loaded inside framework processes. libEGL_<chipset>.so and android.hardware.graphics.mapper@2.0-impl.so, etc are SP-HALs. When framework needs to load those SP-HALs, it explicitly loads it from this namespace using android_get_exported_namespace() and android_dlopen_ext(). vndk namespace is the namespace for loading vndk-sp (Vendor-NDK for Same-Process) libs, which is a small set of framework libraries that SP-HALs can link against. These libraries are compiled for the same version of Android that the vendor partition is compiled against. SP-HALs can not use libraries other than vndk-sp and ndk libs. Membership to vndk-sp and ndk are strictly closed. Note that in a system, there are two copies of vndk-sp libs. One at /system/lib and the other at /vendor/lib/vndk-sp. As a result, there can be two instances of a same library in a process. Also adds ld.config.legacy.txt which is used on non-Treble devices where PRODUCT_FULL_TREBLE is not set to true. Note, this split can be cleaned up further after b/37139976 is solved. Bug: 34407260 Test: git diff HEAD:rootdir/etc/ld.config.legacy.txt HEAD^:rootdir/etc/ld.config.txt => 0 Test: sailfish boots (because BOARD_VNDK_VERSION is not set to 'current') Change-Id: I8331d94edc38f22c4f8abc66cdf2050af9d0605b
2017-04-05 13:24:14 +08:00
# TODO(b/37013858): remove all dependencies to /vendor/lib from system processes
# When this is done, comment out following three lines and remove the three
# lines above
#namespace.default.isolated = true
#namespace.default.search.paths = /system/${LIB}
#namespace.default.permitted.paths = /system/${LIB}
#
#namespace.default.asan.search.paths = /data/asan/system/${LIB}:/system/${LIB}
#namespace.default.asan.permitted.paths = /data/asan/system/${LIB}:/system/${LIB}
Configure ld.config.txt for SP-HALs Now, framework process (any process that is executing /system/bin/* or /system/xbin/*) are started with three namespaces; default, sphal and vndk. default namespace is the namespace that is responsible for loading libs from /system/lib. It can't load libs from other places such as /vendor/lib. (However, we temporarily open the path since we haven't finished the system partition cleanup, but will do eventually). sphal namespace is the namespace where SP-HAL (Same-process HAL) is loaded. SP-HAL are the only vendor libraries that are allowed to be loaded inside framework processes. libEGL_<chipset>.so and android.hardware.graphics.mapper@2.0-impl.so, etc are SP-HALs. When framework needs to load those SP-HALs, it explicitly loads it from this namespace using android_get_exported_namespace() and android_dlopen_ext(). vndk namespace is the namespace for loading vndk-sp (Vendor-NDK for Same-Process) libs, which is a small set of framework libraries that SP-HALs can link against. These libraries are compiled for the same version of Android that the vendor partition is compiled against. SP-HALs can not use libraries other than vndk-sp and ndk libs. Membership to vndk-sp and ndk are strictly closed. Note that in a system, there are two copies of vndk-sp libs. One at /system/lib and the other at /vendor/lib/vndk-sp. As a result, there can be two instances of a same library in a process. Also adds ld.config.legacy.txt which is used on non-Treble devices where PRODUCT_FULL_TREBLE is not set to true. Note, this split can be cleaned up further after b/37139976 is solved. Bug: 34407260 Test: git diff HEAD:rootdir/etc/ld.config.legacy.txt HEAD^:rootdir/etc/ld.config.txt => 0 Test: sailfish boots (because BOARD_VNDK_VERSION is not set to 'current') Change-Id: I8331d94edc38f22c4f8abc66cdf2050af9d0605b
2017-04-05 13:24:14 +08:00
###############################################################################
# "sphal" namespace
#
# SP-HAL(Sameprocess-HAL)s are the only vendor libraries that are allowed to be
# loaded inside system processes. libEGL_<chipset>.so, libGLESv2_<chipset>.so,
# android.hardware.graphics.mapper@2.0-impl.so, etc are SP-HALs.
#
# This namespace is exclusivly for SP-HALs. When the framework tries to dynami-
# cally load SP-HALs, android_dlopen_ext() is used to explicitly specifying
# that they should be searched and loaded from this namespace.
#
# Note that there is no link from the default namespace to this namespace.
###############################################################################
namespace.sphal.isolated = true
namespace.sphal.visible = true
namespace.sphal.search.paths = /vendor/${LIB}/egl:/vendor/${LIB}/hw:/vendor/${LIB}
namespace.sphal.permitted.paths = /vendor/${LIB}
namespace.sphal.asan.search.paths = /data/asan/vendor/${LIB}/egl:/vendor/${LIB}/egl:/data/asan/vendor/${LIB}/hw:/vendor/${LIB}/hw:/data/asan/vendor/${LIB}:/vendor/${LIB}
namespace.sphal.asan.permitted.paths = /data/asan/vendor/${LIB}:/vendor/${LIB}
Configure ld.config.txt for SP-HALs Now, framework process (any process that is executing /system/bin/* or /system/xbin/*) are started with three namespaces; default, sphal and vndk. default namespace is the namespace that is responsible for loading libs from /system/lib. It can't load libs from other places such as /vendor/lib. (However, we temporarily open the path since we haven't finished the system partition cleanup, but will do eventually). sphal namespace is the namespace where SP-HAL (Same-process HAL) is loaded. SP-HAL are the only vendor libraries that are allowed to be loaded inside framework processes. libEGL_<chipset>.so and android.hardware.graphics.mapper@2.0-impl.so, etc are SP-HALs. When framework needs to load those SP-HALs, it explicitly loads it from this namespace using android_get_exported_namespace() and android_dlopen_ext(). vndk namespace is the namespace for loading vndk-sp (Vendor-NDK for Same-Process) libs, which is a small set of framework libraries that SP-HALs can link against. These libraries are compiled for the same version of Android that the vendor partition is compiled against. SP-HALs can not use libraries other than vndk-sp and ndk libs. Membership to vndk-sp and ndk are strictly closed. Note that in a system, there are two copies of vndk-sp libs. One at /system/lib and the other at /vendor/lib/vndk-sp. As a result, there can be two instances of a same library in a process. Also adds ld.config.legacy.txt which is used on non-Treble devices where PRODUCT_FULL_TREBLE is not set to true. Note, this split can be cleaned up further after b/37139976 is solved. Bug: 34407260 Test: git diff HEAD:rootdir/etc/ld.config.legacy.txt HEAD^:rootdir/etc/ld.config.txt => 0 Test: sailfish boots (because BOARD_VNDK_VERSION is not set to 'current') Change-Id: I8331d94edc38f22c4f8abc66cdf2050af9d0605b
2017-04-05 13:24:14 +08:00
# Once in this namespace, access to libraries in /system/lib is restricted. Only
# libs listed here can be used.
namespace.sphal.links = default,vndk,rs
Configure ld.config.txt for SP-HALs Now, framework process (any process that is executing /system/bin/* or /system/xbin/*) are started with three namespaces; default, sphal and vndk. default namespace is the namespace that is responsible for loading libs from /system/lib. It can't load libs from other places such as /vendor/lib. (However, we temporarily open the path since we haven't finished the system partition cleanup, but will do eventually). sphal namespace is the namespace where SP-HAL (Same-process HAL) is loaded. SP-HAL are the only vendor libraries that are allowed to be loaded inside framework processes. libEGL_<chipset>.so and android.hardware.graphics.mapper@2.0-impl.so, etc are SP-HALs. When framework needs to load those SP-HALs, it explicitly loads it from this namespace using android_get_exported_namespace() and android_dlopen_ext(). vndk namespace is the namespace for loading vndk-sp (Vendor-NDK for Same-Process) libs, which is a small set of framework libraries that SP-HALs can link against. These libraries are compiled for the same version of Android that the vendor partition is compiled against. SP-HALs can not use libraries other than vndk-sp and ndk libs. Membership to vndk-sp and ndk are strictly closed. Note that in a system, there are two copies of vndk-sp libs. One at /system/lib and the other at /vendor/lib/vndk-sp. As a result, there can be two instances of a same library in a process. Also adds ld.config.legacy.txt which is used on non-Treble devices where PRODUCT_FULL_TREBLE is not set to true. Note, this split can be cleaned up further after b/37139976 is solved. Bug: 34407260 Test: git diff HEAD:rootdir/etc/ld.config.legacy.txt HEAD^:rootdir/etc/ld.config.txt => 0 Test: sailfish boots (because BOARD_VNDK_VERSION is not set to 'current') Change-Id: I8331d94edc38f22c4f8abc66cdf2050af9d0605b
2017-04-05 13:24:14 +08:00
# WARNING: only NDK libs can be listed here.
# However, this is commented out because some SP-HALs (gralloc.msm8996.so, etc)
# are currently using some non-stable libs such as libbacktrace.so. We will get back
Configure ld.config.txt for SP-HALs Now, framework process (any process that is executing /system/bin/* or /system/xbin/*) are started with three namespaces; default, sphal and vndk. default namespace is the namespace that is responsible for loading libs from /system/lib. It can't load libs from other places such as /vendor/lib. (However, we temporarily open the path since we haven't finished the system partition cleanup, but will do eventually). sphal namespace is the namespace where SP-HAL (Same-process HAL) is loaded. SP-HAL are the only vendor libraries that are allowed to be loaded inside framework processes. libEGL_<chipset>.so and android.hardware.graphics.mapper@2.0-impl.so, etc are SP-HALs. When framework needs to load those SP-HALs, it explicitly loads it from this namespace using android_get_exported_namespace() and android_dlopen_ext(). vndk namespace is the namespace for loading vndk-sp (Vendor-NDK for Same-Process) libs, which is a small set of framework libraries that SP-HALs can link against. These libraries are compiled for the same version of Android that the vendor partition is compiled against. SP-HALs can not use libraries other than vndk-sp and ndk libs. Membership to vndk-sp and ndk are strictly closed. Note that in a system, there are two copies of vndk-sp libs. One at /system/lib and the other at /vendor/lib/vndk-sp. As a result, there can be two instances of a same library in a process. Also adds ld.config.legacy.txt which is used on non-Treble devices where PRODUCT_FULL_TREBLE is not set to true. Note, this split can be cleaned up further after b/37139976 is solved. Bug: 34407260 Test: git diff HEAD:rootdir/etc/ld.config.legacy.txt HEAD^:rootdir/etc/ld.config.txt => 0 Test: sailfish boots (because BOARD_VNDK_VERSION is not set to 'current') Change-Id: I8331d94edc38f22c4f8abc66cdf2050af9d0605b
2017-04-05 13:24:14 +08:00
# to this list once the dependencies are fixed.
#namespace.sphal.link.default.shared_libs = libc.so:libz.so:libm.so:libdl.so:libstdc++.so:liblog.so:libnativewindow.so:libsync.so
namespace.sphal.link.default.shared_libs = libc.so:libz.so:libm.so:libdl.so:libstdc++.so:liblog.so:libnativewindow.so:libEGL.so:libsync.so:libbacktrace.so:libGLESv1_CM.so:libGLESv2.so
Configure ld.config.txt for SP-HALs Now, framework process (any process that is executing /system/bin/* or /system/xbin/*) are started with three namespaces; default, sphal and vndk. default namespace is the namespace that is responsible for loading libs from /system/lib. It can't load libs from other places such as /vendor/lib. (However, we temporarily open the path since we haven't finished the system partition cleanup, but will do eventually). sphal namespace is the namespace where SP-HAL (Same-process HAL) is loaded. SP-HAL are the only vendor libraries that are allowed to be loaded inside framework processes. libEGL_<chipset>.so and android.hardware.graphics.mapper@2.0-impl.so, etc are SP-HALs. When framework needs to load those SP-HALs, it explicitly loads it from this namespace using android_get_exported_namespace() and android_dlopen_ext(). vndk namespace is the namespace for loading vndk-sp (Vendor-NDK for Same-Process) libs, which is a small set of framework libraries that SP-HALs can link against. These libraries are compiled for the same version of Android that the vendor partition is compiled against. SP-HALs can not use libraries other than vndk-sp and ndk libs. Membership to vndk-sp and ndk are strictly closed. Note that in a system, there are two copies of vndk-sp libs. One at /system/lib and the other at /vendor/lib/vndk-sp. As a result, there can be two instances of a same library in a process. Also adds ld.config.legacy.txt which is used on non-Treble devices where PRODUCT_FULL_TREBLE is not set to true. Note, this split can be cleaned up further after b/37139976 is solved. Bug: 34407260 Test: git diff HEAD:rootdir/etc/ld.config.legacy.txt HEAD^:rootdir/etc/ld.config.txt => 0 Test: sailfish boots (because BOARD_VNDK_VERSION is not set to 'current') Change-Id: I8331d94edc38f22c4f8abc66cdf2050af9d0605b
2017-04-05 13:24:14 +08:00
# WARNING: only VNDK-SP libs can be listed here. DO NOT EDIT this line.
namespace.sphal.link.vndk.shared_libs = android.hardware.renderscript@1.0.so:android.hardware.graphics.allocator@2.0.so:android.hardware.graphics.mapper@2.0.so:android.hardware.graphics.common@1.0.so:android.hidl.base@1.0.so:libhwbinder.so:libbase.so:libcutils.so:libhardware.so:libhidlbase.so:libhidltransport.so:libutils.so:libc++.so
# Renderscript gets separate namespace
namespace.sphal.link.rs.shared_libs = libRS_internal.so
###############################################################################
# "rs" namespace
#
# This namespace is exclusively for Renderscript internal libraries.
# This namespace has slightly looser restriction than the vndk namespace because
# of the genuine characteristics of Renderscript; /data is in the permitted path
# to load the compiled *.so file and libmediandk.so can be used here.
###############################################################################
namespace.rs.isolated = true
namespace.rs.search.paths = /system/${LIB}/vndk-sp:/vendor/${LIB}
namespace.rs.permitted.paths = /vendor/${LIB}:/data
namespace.rs.links = default,vndk
namespace.rs.link.default.shared_libs = libc.so:libz.so:libm.so:libdl.so:libstdc++.so:liblog.so:libnativewindow.so:libEGL.so:libsync.so:libbacktrace.so:libGLESv1_CM.so:libGLESv2.so:libmediandk.so:libui.so
namespace.rs.link.vndk.shared_libs = android.hardware.renderscript@1.0.so:android.hardware.graphics.allocator@2.0.so:android.hardware.graphics.mapper@2.0.so:android.hardware.graphics.common@1.0.so:android.hidl.base@1.0.so:libhwbinder.so:libbase.so:libcutils.so:libhardware.so:libhidlbase.so:libhidltransport.so:libutils.so:libc++.so
Configure ld.config.txt for SP-HALs Now, framework process (any process that is executing /system/bin/* or /system/xbin/*) are started with three namespaces; default, sphal and vndk. default namespace is the namespace that is responsible for loading libs from /system/lib. It can't load libs from other places such as /vendor/lib. (However, we temporarily open the path since we haven't finished the system partition cleanup, but will do eventually). sphal namespace is the namespace where SP-HAL (Same-process HAL) is loaded. SP-HAL are the only vendor libraries that are allowed to be loaded inside framework processes. libEGL_<chipset>.so and android.hardware.graphics.mapper@2.0-impl.so, etc are SP-HALs. When framework needs to load those SP-HALs, it explicitly loads it from this namespace using android_get_exported_namespace() and android_dlopen_ext(). vndk namespace is the namespace for loading vndk-sp (Vendor-NDK for Same-Process) libs, which is a small set of framework libraries that SP-HALs can link against. These libraries are compiled for the same version of Android that the vendor partition is compiled against. SP-HALs can not use libraries other than vndk-sp and ndk libs. Membership to vndk-sp and ndk are strictly closed. Note that in a system, there are two copies of vndk-sp libs. One at /system/lib and the other at /vendor/lib/vndk-sp. As a result, there can be two instances of a same library in a process. Also adds ld.config.legacy.txt which is used on non-Treble devices where PRODUCT_FULL_TREBLE is not set to true. Note, this split can be cleaned up further after b/37139976 is solved. Bug: 34407260 Test: git diff HEAD:rootdir/etc/ld.config.legacy.txt HEAD^:rootdir/etc/ld.config.txt => 0 Test: sailfish boots (because BOARD_VNDK_VERSION is not set to 'current') Change-Id: I8331d94edc38f22c4f8abc66cdf2050af9d0605b
2017-04-05 13:24:14 +08:00
###############################################################################
# "vndk" namespace
#
# This namespace is exclusively for vndk-sp libs.
###############################################################################
namespace.vndk.isolated = true
namespace.vndk.search.paths = /system/${LIB}/vndk-sp:/vendor/${LIB}
Configure ld.config.txt for SP-HALs Now, framework process (any process that is executing /system/bin/* or /system/xbin/*) are started with three namespaces; default, sphal and vndk. default namespace is the namespace that is responsible for loading libs from /system/lib. It can't load libs from other places such as /vendor/lib. (However, we temporarily open the path since we haven't finished the system partition cleanup, but will do eventually). sphal namespace is the namespace where SP-HAL (Same-process HAL) is loaded. SP-HAL are the only vendor libraries that are allowed to be loaded inside framework processes. libEGL_<chipset>.so and android.hardware.graphics.mapper@2.0-impl.so, etc are SP-HALs. When framework needs to load those SP-HALs, it explicitly loads it from this namespace using android_get_exported_namespace() and android_dlopen_ext(). vndk namespace is the namespace for loading vndk-sp (Vendor-NDK for Same-Process) libs, which is a small set of framework libraries that SP-HALs can link against. These libraries are compiled for the same version of Android that the vendor partition is compiled against. SP-HALs can not use libraries other than vndk-sp and ndk libs. Membership to vndk-sp and ndk are strictly closed. Note that in a system, there are two copies of vndk-sp libs. One at /system/lib and the other at /vendor/lib/vndk-sp. As a result, there can be two instances of a same library in a process. Also adds ld.config.legacy.txt which is used on non-Treble devices where PRODUCT_FULL_TREBLE is not set to true. Note, this split can be cleaned up further after b/37139976 is solved. Bug: 34407260 Test: git diff HEAD:rootdir/etc/ld.config.legacy.txt HEAD^:rootdir/etc/ld.config.txt => 0 Test: sailfish boots (because BOARD_VNDK_VERSION is not set to 'current') Change-Id: I8331d94edc38f22c4f8abc66cdf2050af9d0605b
2017-04-05 13:24:14 +08:00
namespace.vndk.permitted.paths = /vendor/${LIB}/hw:/vendor/${LIB}/egl
namespace.vndk.asan.search.paths = /data/asan/vendor/${LIB}/vndk-sp:/vendor/${LIB}/vndk-sp:/data/asan/vendor/${LIB}:/vendor/${LIB}
namespace.vndk.asan.permitted.paths = /data/asan/vendor/${LIB}/hw:/vendor/${LIB}/hw:/data/asan/vendor/${LIB}/egl:/vendor/${LIB}/egl
Configure ld.config.txt for SP-HALs Now, framework process (any process that is executing /system/bin/* or /system/xbin/*) are started with three namespaces; default, sphal and vndk. default namespace is the namespace that is responsible for loading libs from /system/lib. It can't load libs from other places such as /vendor/lib. (However, we temporarily open the path since we haven't finished the system partition cleanup, but will do eventually). sphal namespace is the namespace where SP-HAL (Same-process HAL) is loaded. SP-HAL are the only vendor libraries that are allowed to be loaded inside framework processes. libEGL_<chipset>.so and android.hardware.graphics.mapper@2.0-impl.so, etc are SP-HALs. When framework needs to load those SP-HALs, it explicitly loads it from this namespace using android_get_exported_namespace() and android_dlopen_ext(). vndk namespace is the namespace for loading vndk-sp (Vendor-NDK for Same-Process) libs, which is a small set of framework libraries that SP-HALs can link against. These libraries are compiled for the same version of Android that the vendor partition is compiled against. SP-HALs can not use libraries other than vndk-sp and ndk libs. Membership to vndk-sp and ndk are strictly closed. Note that in a system, there are two copies of vndk-sp libs. One at /system/lib and the other at /vendor/lib/vndk-sp. As a result, there can be two instances of a same library in a process. Also adds ld.config.legacy.txt which is used on non-Treble devices where PRODUCT_FULL_TREBLE is not set to true. Note, this split can be cleaned up further after b/37139976 is solved. Bug: 34407260 Test: git diff HEAD:rootdir/etc/ld.config.legacy.txt HEAD^:rootdir/etc/ld.config.txt => 0 Test: sailfish boots (because BOARD_VNDK_VERSION is not set to 'current') Change-Id: I8331d94edc38f22c4f8abc66cdf2050af9d0605b
2017-04-05 13:24:14 +08:00
# When these NDK libs are required inside this namespace, then it is redirected
# to the default namespace. This is possible since their ABI is stable across
# Android releases.
namespace.vndk.links = default
# WARNING: only NDK libs can be listed here.
# However, this is commented out because some SP-HALs (gralloc.msm8996.so, etc)
# are currently using some non-stable libs such as libbacktrace.so. We will get back
Configure ld.config.txt for SP-HALs Now, framework process (any process that is executing /system/bin/* or /system/xbin/*) are started with three namespaces; default, sphal and vndk. default namespace is the namespace that is responsible for loading libs from /system/lib. It can't load libs from other places such as /vendor/lib. (However, we temporarily open the path since we haven't finished the system partition cleanup, but will do eventually). sphal namespace is the namespace where SP-HAL (Same-process HAL) is loaded. SP-HAL are the only vendor libraries that are allowed to be loaded inside framework processes. libEGL_<chipset>.so and android.hardware.graphics.mapper@2.0-impl.so, etc are SP-HALs. When framework needs to load those SP-HALs, it explicitly loads it from this namespace using android_get_exported_namespace() and android_dlopen_ext(). vndk namespace is the namespace for loading vndk-sp (Vendor-NDK for Same-Process) libs, which is a small set of framework libraries that SP-HALs can link against. These libraries are compiled for the same version of Android that the vendor partition is compiled against. SP-HALs can not use libraries other than vndk-sp and ndk libs. Membership to vndk-sp and ndk are strictly closed. Note that in a system, there are two copies of vndk-sp libs. One at /system/lib and the other at /vendor/lib/vndk-sp. As a result, there can be two instances of a same library in a process. Also adds ld.config.legacy.txt which is used on non-Treble devices where PRODUCT_FULL_TREBLE is not set to true. Note, this split can be cleaned up further after b/37139976 is solved. Bug: 34407260 Test: git diff HEAD:rootdir/etc/ld.config.legacy.txt HEAD^:rootdir/etc/ld.config.txt => 0 Test: sailfish boots (because BOARD_VNDK_VERSION is not set to 'current') Change-Id: I8331d94edc38f22c4f8abc66cdf2050af9d0605b
2017-04-05 13:24:14 +08:00
# to this list once the dependencies are fixed.
#namespace.vndk.link.default.shared_libs = libc.so:libz.so:libm.so:libdl.so:libstdc++.so:liblog.so:libnativewindow.so:libsync.so
namespace.vndk.link.default.shared_libs = libc.so:libz.so:libm.so:libdl.so:libstdc++.so:liblog.so:libnativewindow.so:libEGL.so:libsync.so:libbacktrace.so
Configure ld.config.txt for SP-HALs Now, framework process (any process that is executing /system/bin/* or /system/xbin/*) are started with three namespaces; default, sphal and vndk. default namespace is the namespace that is responsible for loading libs from /system/lib. It can't load libs from other places such as /vendor/lib. (However, we temporarily open the path since we haven't finished the system partition cleanup, but will do eventually). sphal namespace is the namespace where SP-HAL (Same-process HAL) is loaded. SP-HAL are the only vendor libraries that are allowed to be loaded inside framework processes. libEGL_<chipset>.so and android.hardware.graphics.mapper@2.0-impl.so, etc are SP-HALs. When framework needs to load those SP-HALs, it explicitly loads it from this namespace using android_get_exported_namespace() and android_dlopen_ext(). vndk namespace is the namespace for loading vndk-sp (Vendor-NDK for Same-Process) libs, which is a small set of framework libraries that SP-HALs can link against. These libraries are compiled for the same version of Android that the vendor partition is compiled against. SP-HALs can not use libraries other than vndk-sp and ndk libs. Membership to vndk-sp and ndk are strictly closed. Note that in a system, there are two copies of vndk-sp libs. One at /system/lib and the other at /vendor/lib/vndk-sp. As a result, there can be two instances of a same library in a process. Also adds ld.config.legacy.txt which is used on non-Treble devices where PRODUCT_FULL_TREBLE is not set to true. Note, this split can be cleaned up further after b/37139976 is solved. Bug: 34407260 Test: git diff HEAD:rootdir/etc/ld.config.legacy.txt HEAD^:rootdir/etc/ld.config.txt => 0 Test: sailfish boots (because BOARD_VNDK_VERSION is not set to 'current') Change-Id: I8331d94edc38f22c4f8abc66cdf2050af9d0605b
2017-04-05 13:24:14 +08:00
[vendor]
namespace.default.isolated = false
namespace.default.search.paths = /vendor/${LIB}:/vendor/${LIB}/vndk-sp:/system/${LIB}
namespace.default.asan.search.paths = /data/asan/vendor/${LIB}:/vendor/${LIB}:/data/asan/vendor/${LIB}/vndk-sp:/vendor/${LIB}/vndk-sp:/data/asan/system/${LIB}:/system/${LIB}