commit | c502af5b9c88c558c5db33aa9e46490984a60b30 | [log] [tgz] |
---|---|---|
author | Kiyoung Kim <kiyoungkim@google.com> | Tue Dec 08 16:17:50 2020 +0900 |
committer | Kiyoung Kim <kiyoungkim@google.com> | Wed Jan 20 14:07:17 2021 +0900 |
tree | 71a6bbacb74bcbc4f3e5c0f007860b0ed404b139 | |
parent | 6c7494c7805ffda04744f9d67c63bd192faa81d0 [diff] |
Verify extra paths from APEX linker config Extra paths from APEX linker config cannot be verified from linkerconfig code review. To make sure if path is valid, this change checks if all extra paths are valid paths. Bug: 175655717 Test: m -j passed && atest passed Change-Id: I96740638b240a24a1eafa7def354cc9eebcd15e1
Linkerconfig is a program to generate linker configuration based on the runtime environment. Linkerconfig generates one or more ld.config.txt files and some other files under /linkerconfig during init. Linker will read this generated configuration file(s) to find out link relationship between libraries and executable.
TODO: explain inputs (e.g. /system/etc/public.libraries.txt, /apex/apex-info-list.xml, ..)
Linker configuration file can be used to add extra information while linkerconfig creates linker configuration with the module. This module can be defined as ‘linker_config’ from Soong, and it will be translated as protobuf file at build time.
linker.config.json file is in json format which can contain properties as below.
Property Name | Type | Description | Allowed module |
---|---|---|---|
permittedPaths | List | Additional permitted paths | APEX |
visible | bool | Force APEX namespace to be visible from all sections if the value is true | APEX |
provideLibs | List | Libraries providing from the module | System |
requireLibs | List | Libraries required from the module | System |
{ "permittedPaths" : [ "/a", "/b/c", "/d/e/f"], "visible": true }
{ "provideLibs" : [ "a.so", "b.so", "c.so" ], "requireLibs" : [ "foo.so", "bar.so", "baz.so" ] }
TODO: a few words about the files
Check ld.config.format.md.
The file describes libraries exposed from APEXes. libnativeloader is the main consumer of this file.
# comment line jni com_android_foo libfoo_jni.so public com_android_bar libbar.so:libbaz.so
The file is line-based and each line consists of tag apex_namespace library_list
.
tag
explains what library_list
is.apex_namespace
is the namespace of the apex. Note that it is mangled like com_android_foo
for the APEX(“com.android.foo”).library_list
is colon-separated list of library names.tag
is jni
, library_list
is the list of JNI libraries exposed by apex_namespace
.tag
is public
, library_list
is the list of public libraries exposed by apex_namespace
. Here, public libraries are the libs listed in /system/etc/public.libraries.txt.