<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-clang.git/dynamic-layers, branch scarthgap</title>
<subtitle>Mirror of github.com/kraj/meta-clang.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-clang.git/atom?h=scarthgap</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-clang.git/atom?h=scarthgap'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/'/>
<updated>2025-12-12T04:21:23+00:00</updated>
<entry>
<title>bpftrace 0.20.1: Fix CVE-2024-2313</title>
<updated>2025-12-12T04:21:23+00:00</updated>
<author>
<name>Deepak Rathore</name>
<email>deeratho@cisco.com</email>
</author>
<published>2025-11-27T11:52:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=8cbb4ae395d31c7ad178302126a497f7a1477b5b'/>
<id>urn:sha1:8cbb4ae395d31c7ad178302126a497f7a1477b5b</id>
<content type='text'>
Upstream Repository: https://github.com/bpftrace/bpftrace.git

Bug Details: https://nvd.nist.gov/vuln/detail/CVE-2024-2313
Type: Security Fix
CVE: CVE-2024-2313
Score: 2.8
Patch: https://github.com/bpftrace/bpftrace/commit/bc73244963f2

Note:
- This CVE was initially addressed via commit 4be4b7191acb [1], which
  added ownership verification for unpacked kernel headers.
- The fix was deemed insufficient and a revised comprehensive fix was
  implemented in commit bc73244963f2 [2], which completely removes the
  risky functionality.
- This patch applies only the revised fix (bc73244963f2) which supersedes
  the initial partial fix.

Reference:
[1] https://github.com/bpftrace/bpftrace/pull/3033
[2] https://github.com/bpftrace/bpftrace/pull/3156

Signed-off-by: Deepak Rathore &lt;deeratho@cisco.com&gt;
</content>
</entry>
<entry>
<title>bpftrace: fix buildpaths QA issues</title>
<updated>2025-06-20T20:00:12+00:00</updated>
<author>
<name>Archana Polampalli</name>
<email>archana.polampalli@windriver.com</email>
</author>
<published>2025-06-11T06:30:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=eea5ec23155cfd47781599fdc9a92c21e4caffc8'/>
<id>urn:sha1:eea5ec23155cfd47781599fdc9a92c21e4caffc8</id>
<content type='text'>
* Avoid line statements from bison to fix:
  WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/src/debug/bpftrace/0.21.2+git/parser.tab.cc in package bpftrace-src contains reference to TMPDIR [buildpaths]
  WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/src/debug/bpftrace/0.21.2+git/location.hh in package bpftrace-src contains reference to TMPDIR [buildpaths]
  WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/src/debug/bpftrace/0.21.2+git/parser.tab.hh in package bpftrace-src contains reference to TMPDIR [buildpaths]
  WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/src/debug/bpftrace/0.21.2+git/lex.yy.cc in package bpftrace-src contains reference to TMPDIR [buildpaths]

* there are still few more buildpaths issues with ptest enabled:
  WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/src/debug/bpftrace/0.21.2+git/tests/data/dwarf_data.h in package bpftrace-src contains reference to TMPDIR [buildpaths]
  WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/lib/bpftrace/ptest/tests/.debug/bpftrace_test in package bpftrace-dbg contains reference to TMPDIR [buildpaths]
  WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/lib/bpftrace/ptest/tests/bpftrace_test in package bpftrace-ptest contains reference to TMPDIR [buildpaths]
  WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/lib/bpftrace/ptest/tests/testlibs/cmake_install.cmake in package bpftrace-ptest contains reference to TMPDIR [buildpaths]
  WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/lib/bpftrace/ptest/tests/testlibs/CTestTestfile.cmake in package bpftrace-ptest contains reference to TMPDIR [buildpaths]
  WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/lib/bpftrace/ptest/tests/testprogs/cmake_install.cmake in package bpftrace-ptest contains reference to TMPDIR [buildpaths]
  WARNING: bpftrace-0.21.2+git-r0 do_package_qa: QA Issue: File /usr/lib/bpftrace/ptest/tests/testprogs/CTestTestfile.cmake in package bpftrace-ptest contains reference to TMPDIR [buildpaths]

* lower buildpaths from ERROR_QA to WARN_QA when ptest is enabled
  fixing .cmake files might be simple, but the embedded path to dwarf_data.h
  in bpftrace_test will be more complicated, so will leave it to
  someone actually using bpftrace (and its ptest).

  bpftrace/0.21.2+git/package $ grep -R styhead .
  ./usr/lib/bpftrace/ptest/tests/testlibs/cmake_install.cmake:# Install script for directory: ${WORKDIR}/git/tests/testlibs
  ./usr/lib/bpftrace/ptest/tests/testlibs/cmake_install.cmake:  set(CMAKE_OBJDUMP "${WORKDIR}/recipe-sysroot-native/usr/bin/aarch64-webos-linux/aarch64-webos-linux-objdump")
  ./usr/lib/bpftrace/ptest/tests/testlibs/CTestTestfile.cmake:# Source directory: ${WORKDIR}/git/tests/testlibs
  ./usr/lib/bpftrace/ptest/tests/testlibs/CTestTestfile.cmake:# Build directory: ${WORKDIR}/build/tests/testlibs
  grep: ./usr/lib/bpftrace/ptest/tests/.debug/bpftrace_test: binary file matches
  grep: ./usr/lib/bpftrace/ptest/tests/bpftrace_test: binary file matches
  ./usr/lib/bpftrace/ptest/tests/testprogs/cmake_install.cmake:# Install script for directory: ${WORKDIR}/git/tests/testprogs
  ./usr/lib/bpftrace/ptest/tests/testprogs/cmake_install.cmake:  set(CMAKE_OBJDUMP "${WORKDIR}/recipe-sysroot-native/usr/bin/aarch64-webos-linux/aarch64-webos-linux-objdump")
  ./usr/lib/bpftrace/ptest/tests/testprogs/CTestTestfile.cmake:# Source directory: ${WORKDIR}/git/tests/testprogs
  ./usr/lib/bpftrace/ptest/tests/testprogs/CTestTestfile.cmake:# Build directory: ${WORKDIR}/build/tests/testprogs
  ./usr/src/debug/bpftrace/0.21.2+git/tests/data/dwarf_data.h:constexpr inline const char *dwarf_data_cxx_path = "${WORKDIR}/build/tests/data/data_source_cxx";

Signed-off-by: Martin Jansa &lt;martin.jansa@gmail.com&gt;

Signed-off-by: Archana Polampalli &lt;archana.polampalli@windriver.com&gt;
</content>
</entry>
<entry>
<title>bpftrace: move from dynamic-layers/openembedded-layer to dynamic-layers/meta-python</title>
<updated>2025-06-20T20:00:12+00:00</updated>
<author>
<name>Archana Polampalli</name>
<email>archana.polampalli@windriver.com</email>
</author>
<published>2025-06-06T05:51:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=525625cb266c8a6ea9a4ddedabf935c825d38510'/>
<id>urn:sha1:525625cb266c8a6ea9a4ddedabf935c825d38510</id>
<content type='text'>
* bpftrace itself doesn't depend on meta-python, but
  bpftrace from dynamic-layers/openembedded-layer depends on bcc from dynamic-layers/meta-python
  so better to move it there. This way both bcc and bpftrace are either both available
  at the same time or neither of them.

* fixes https://github.com/kraj/meta-clang/issues/985

  ERROR: Nothing PROVIDES 'bcc' (but /mnt/secondary/poky/meta-clang/dynamic-layers/openembedded-layer/recipes-devtools/bpftrace/bpftrace_0.20.1.bb DEPENDS on or otherwise requires it). Close matches:
    bc
    byacc
  NOTE: Runtime target 'bpftrace' is unbuildable, removing...
  Missing or unbuildable dependency chain was: ['bpftrace', 'bcc']
  ERROR: Required build target 'core-image-minimal' has no buildable providers.
  Missing or unbuildable dependency chain was: ['core-image-minimal', 'bpftrace', 'bcc']

  when only openembedded-layer (meta-oe) is in BBLAYERS and meta-python isn't.

Signed-off-by: Martin Jansa &lt;martin.jansa@gmail.com&gt;

Signed-off-by: Archana Polampalli &lt;archana.polampalli@windriver.com&gt;
</content>
</entry>
<entry>
<title>bcc: fix CVE-2024-2314</title>
<updated>2025-04-11T00:54:52+00:00</updated>
<author>
<name>Divya Chellam</name>
<email>divya.chellam@windriver.com</email>
</author>
<published>2025-04-04T01:38:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=eaa08939eaec9f620b14742ff3ac568553683034'/>
<id>urn:sha1:eaa08939eaec9f620b14742ff3ac568553683034</id>
<content type='text'>
If kernel headers need to be extracted, bcc will attempt to load them
from a temporary directory. An unprivileged attacker could use this to
force bcc to load compromised linux headers. Linux distributions which
provide kernel headers by default are not affected by default.

Reference:
https://nvd.nist.gov/vuln/detail/CVE-2024-2314

Upstream-patch:
https://github.com/iovisor/bcc/commit/008ea09e891194c072f2a9305a3c872a241dc342

Signed-off-by: Divya Chellam &lt;divya.chellam@windriver.com&gt;
</content>
</entry>
<entry>
<title>bpftrace: fix the runtime ptest errors</title>
<updated>2024-04-10T02:34:12+00:00</updated>
<author>
<name>Wentao Zhang</name>
<email>wentao.zhang@windriver.com</email>
</author>
<published>2024-04-09T06:25:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=c38281d2c4c5725ab4d3d07de7738b80ad0d8bbc'/>
<id>urn:sha1:c38281d2c4c5725ab4d3d07de7738b80ad0d8bbc</id>
<content type='text'>
https://github.com/bpftrace/bpftrace/pull/2935 changed the test scripts,
then the runtime ptest got the following errors:
| KeyError: 'BPFTRACE_AOT_RUNTIME_TEST_EXECUTABLE'
| Output: /bin/sh: line 1: /usr/bin/: Is a directory\n
The changes in run-ptest is to solve these problems.

After fixing the previously mentioned problems,
we got the the following errors while running the runtime ptest:
| error: &lt;unknown&gt;:0:0: in function BEGIN i64 (ptr): 0x56056cec80f0: i64 = GlobalAddress&lt;ptr @__atomic_compare_exchange&gt; 0 too many arguments
The new patch in the bb file is to solve this problem.

Signed-off-by: Wentao Zhang &lt;wentao.zhang@windriver.com&gt;
</content>
</entry>
<entry>
<title>qt6/qttools: remove bbappend</title>
<updated>2024-03-21T19:08:12+00:00</updated>
<author>
<name>Samuli Piippo</name>
<email>samuli.piippo@qt.io</email>
</author>
<published>2024-03-21T13:25:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=efec5edb798c23329c62c0a86264bc02ebe1dd0a'/>
<id>urn:sha1:efec5edb798c23329c62c0a86264bc02ebe1dd0a</id>
<content type='text'>
clang dependency is already added in meta-qt6 recipe.

Signed-off-by: Samuli Piippo &lt;samuli.piippo@qt.io&gt;
</content>
</entry>
<entry>
<title>bcc: remove LUAJIT setting and related examples</title>
<updated>2024-03-18T21:15:16+00:00</updated>
<author>
<name>Changqing Li</name>
<email>changqing.li@windriver.com</email>
</author>
<published>2024-03-15T09:24:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=8e6be2c5abe7d70858c3116458e48f9fb14a7dc4'/>
<id>urn:sha1:8e6be2c5abe7d70858c3116458e48f9fb14a7dc4</id>
<content type='text'>
Current LUAJIT actually not works, below is snip of src/lua/CMakeLists.txt
[snip]
find_package(LuaJIT)
find_program(LUAJIT luajit)

if (LUAJIT_LIBRARIES AND LUAJIT)
	FILE(GLOB_RECURSE SRC_LUA
		${CMAKE_CURRENT_SOURCE_DIR}/bcc/*.lua
		${CMAKE_CURRENT_SOURCE_DIR}/bcc/vendor/*.lua
		${CMAKE_CURRENT_SOURCE_DIR}/bpf/*.lua)

	ADD_CUSTOM_COMMAND(
		OUTPUT bcc.lua
		COMMAND ${LUAJIT} ${CMAKE_CURRENT_SOURCE_DIR}/src/squish.lua ${CMAKE_CURRENT_SOURCE_DIR}
		DEPENDS ${SRC_LUA} ${CMAKE_CURRENT_SOURCE_DIR}/squishy
	)

	ADD_CUSTOM_COMMAND(
		OUTPUT bcc.o
		COMMAND ${LUAJIT} -bg bcc.lua bcc.o
		DEPENDS bcc.lua
	)
[snip]

LUAJIT will be set when luajit is found. For oe, maybe we need to
DEPENDS on luajit-native. But there are still 2 problems after I change
DEPENDS from luajit to luajit-native and export
LUA_PATH="${RECIPE_SYSROOT_NATIVE}/usr/share/luajit-2.1/?.lua"

1. luajit seems not support cross compile, if our target arch is
different with build host, from above snip, luajit will compile out
bcc.o with host arch, int this way, compile will failed with below
error: "error adding symbols: file in wrong format".

Refer [1],  seems like option "-a" can used to generate other arch
object. But luajit-native don't have this option:
cortexa57-wrs-linux/bcc/0.29.1/recipe-sysroot-native/usr/bin/luajit [options]... [script [args]...].
Available options are:
-e chunk Execute string 'chunk'.
-l name Require library 'name'.
-b ... Save or list bytecode.
-j cmd Perform LuaJIT control command.
-O[opt] Control LuaJIT optimizations.
-i Enter interactive mode after executing 'script'.
-v Show version information.
-E Ignore environment variables.
– Stop handling options.

2. if target arch is the same as build host(my test env is x86-64),
bcc-lua is built out, but still have 2 problems, first, "bcc-lua
/usr/share/bcc/examples/lua/bashreadline.lua" has a runtime error [2].
second, bcc-lua may try to find modules on host path:

root@qemux86-64:/usr/share/bcc/examples/lua# bcc-lua ./kprobe-latency.lua
bcc-lua: bcc.lua:3052: module 'syscall' not found:
no field package.preload['syscall']
no file './syscall.lua'
no file '/build/tmp-glibc/work/x86_64-linux/luajit-native/2.1/recipe-sysroot-native/usr/share/luaj'
no file '/usr/local/share/lua/5.1/syscall.lua'
no file '/usr/local/share/lua/5.1/syscall/init.lua'
no file '/build/tmp-glibc/work/x86_64-linux/luajit-native/2.1/recipe-sysroot-native/usr/share/lua/'
no file '/build/tmp-glibc/work/x86_64-linux/luajit-native/2.1/recipe-sysroot-native/usr/share/lua/'
no file './syscall.so'
no file '/usr/local/lib/lua/5.1/syscall.so'
no file '/build/tmp-glibc/work/x86_64-linux/luajit-native/2.1/recipe-sysroot-native/usr/lib/lua/5.'
no file '/usr/local/lib/lua/5.1/loadall.so'

so remove LUAJIT setting and related examples first

[1] https://luajit.org/running.html
[2] https://github.com/iovisor/bcc/issues/1621

Signed-off-by: Changqing Li &lt;changqing.li@windriver.com&gt;
</content>
</entry>
<entry>
<title>bpftrace: Upgrade to 0.20+ and fix with llvm 18</title>
<updated>2024-03-07T03:18:22+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2024-02-16T18:51:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=57e06fb428e50e349e2e7af26c537047164ab7de'/>
<id>urn:sha1:57e06fb428e50e349e2e7af26c537047164ab7de</id>
<content type='text'>
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>bcc: Do not set LLVM_PACKAGE_VERSION explicitly</title>
<updated>2024-03-07T03:18:22+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2024-02-16T03:14:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=22235606aa2d61bbbc0c4bcc684cb665c5657053'/>
<id>urn:sha1:22235606aa2d61bbbc0c4bcc684cb665c5657053</id>
<content type='text'>
bcc's build system can detect it correctly these days from sysroot cmake
files provided by llvm.

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>bpftool: Add dependency on clang-libllvm</title>
<updated>2024-02-02T00:32:22+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2024-02-01T07:22:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=03fb470c6090bb306870ea787fa42c6ce0337ed0'/>
<id>urn:sha1:03fb470c6090bb306870ea787fa42c6ce0337ed0</id>
<content type='text'>
Provides libLLVM when using clang

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
</feed>
