diff options
| author | Quentin Schulz <quentin.schulz@cherry.de> | 2025-09-04 16:03:39 +0200 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2025-09-11 11:31:56 +0100 |
| commit | 6e54c8c7ff5052a2b67dcda23b48fe213bf95eaa (patch) | |
| tree | b1f9cf81e17b7ddfdab076f36d37e61488c110ea /scripts/lib/buildstats.py | |
| parent | 83987d100dc716b326064b8486376992b7fd453a (diff) | |
| download | poky-6e54c8c7ff5052a2b67dcda23b48fe213bf95eaa.tar.gz | |
mesa: avoid host paths poisoning
At least panfrost and asahi drivers are prone to host paths poisoning
due to unpatched __FILE__ macro in assert() of libcl.
The compilation units for files including this file all are passed
specific arguments via the cl_args meson variable which currently only
contains one fmacro-prefix-map entry for relative paths. However, there
are also absolute build and source paths that seem to make it to the
generated files and libraries so this patches mesa to also strip those
paths.
Note that out of the four paths in the default DEBUG_PREFIX_MAP, only
the source and build directories make it to the fmacro-prefix-map and
they aren't mapped like they are when used with ffile-prefix-map in
DEBUG_PREFIX_MAP as I'm not sure if it is at all possible for meson to
fetch this Yocto-provided path we should be mapping to in the current
mesa code base. I guess this is good enough for now.
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Tested-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
(From OE-Core rev: 5948e618b7746ac333c1ec3ca99b66bd3faeb2ba)
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/lib/buildstats.py')
0 files changed, 0 insertions, 0 deletions