<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-clang.git/dynamic-layers/openembedded-layer, branch kirkstone</title>
<subtitle>Mirror of github.com/kraj/meta-clang.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-clang.git/atom?h=kirkstone</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-clang.git/atom?h=kirkstone'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/'/>
<updated>2025-04-11T00:55:17+00:00</updated>
<entry>
<title>bcc: fix CVE-2024-2314</title>
<updated>2025-04-11T00:55:17+00:00</updated>
<author>
<name>Divya Chellam</name>
<email>divya.chellam@windriver.com</email>
</author>
<published>2025-04-08T04:45:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=8a1d0a1993040ab9d2fb7259b71e4c9582f5cd17'/>
<id>urn:sha1:8a1d0a1993040ab9d2fb7259b71e4c9582f5cd17</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: Simplify ptest script and use posix syntax</title>
<updated>2022-11-03T17:09:11+00:00</updated>
<author>
<name>Michal Wojcik</name>
<email>michal.wojcik@linaro.org</email>
</author>
<published>2022-10-18T09:09:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=ede6ff1ceabb67d075c2ab5f851af5a7b5a9e447'/>
<id>urn:sha1:ede6ff1ceabb67d075c2ab5f851af5a7b5a9e447</id>
<content type='text'>
Signed-off-by: Michal Wojcik &lt;michal.wojcik@linaro.org&gt;
</content>
</entry>
<entry>
<title>bpftrace: Disable ptests on riscv64</title>
<updated>2022-11-03T17:09:11+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2022-10-19T18:05:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=a0cfbec15cc9da8180d22202e13ec464eab047c8'/>
<id>urn:sha1:a0cfbec15cc9da8180d22202e13ec464eab047c8</id>
<content type='text'>
Clang crashes compiling some tests so until its fixed in riscv64 backend
we have to disable it for atleast rv64

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>bcc: Add ptest support</title>
<updated>2022-11-03T17:09:11+00:00</updated>
<author>
<name>Michal Wojcik</name>
<email>michal.wojcik@linaro.org</email>
</author>
<published>2022-10-14T13:29:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=4224316bf823028b367c72d3d46d12f5895c30ae'/>
<id>urn:sha1:4224316bf823028b367c72d3d46d12f5895c30ae</id>
<content type='text'>
Use bcc cc and python test suites and parse their results in ptest form.
Running whole suite on qemu may take up to 25 minutes, so running it
with "ptest-runner -t 1800 bcc" is recommended.

Signed-off-by: Michal Wojcik &lt;michal.wojcik@linaro.org&gt;
</content>
</entry>
<entry>
<title>bpftrace: Add ptest support</title>
<updated>2022-09-30T18:01:53+00:00</updated>
<author>
<name>Michal Wojcik</name>
<email>michal.wojcik@linaro.org</email>
</author>
<published>2022-09-16T13:41:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=c728c3f9168c8a4ed05163a51dd48ca1ad8ac21d'/>
<id>urn:sha1:c728c3f9168c8a4ed05163a51dd48ca1ad8ac21d</id>
<content type='text'>
Use existing bpftrace unit and runtime tests and parse their results in
ptest form.
Running whole suite may take up to 40 minutes, so running it with
"ptest-runner -t 2400 bpftrace" is recommended.

Signed-off-by: Michal Wojcik &lt;michal.wojcik@linaro.org&gt;
</content>
</entry>
<entry>
<title>bcc: De-vendor libbpf</title>
<updated>2022-09-03T21:16:53+00:00</updated>
<author>
<name>Daniel Thompson</name>
<email>daniel@redfelineninja.org.uk</email>
</author>
<published>2022-05-19T09:37:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=3d63d0fd6296e23c7cbbae431e20aa3985ec69dd'/>
<id>urn:sha1:3d63d0fd6296e23c7cbbae431e20aa3985ec69dd</id>
<content type='text'>
Currently bcc builds against a vendored copy of libbpf. This causes
problems for bpftrace which is built against bcc and the system libbpf.
The resulting version skew between the vendored and system versions of
libbpf resulting in a SEGV whenever bpftrace is used.

Although --help and -l (list probe points) work OK that is because they do
not actually use BPF! Anything that does use BPF will crash immediately,
including bpftrace --info and simple one-liners such as:

    ~# bpftrace -e 't:raw_syscalls:sys_exit { printf("%s", comm); }'
    Attaching 1 probe...
    Segmentation fault

Note that this issue is very closely related to similar problems
compiling bpftrace against mixed headers from the two libbpf versions.

Fixes: https://github.com/iovisor/bpftrace/issues/2173
Fixes: bb3e56b06f9d ("bpftrace: Fix build with new libbpf")

Signed-off-by: Daniel Thompson &lt;daniel.thompson@linaro.org&gt;
</content>
</entry>
<entry>
<title>bcc: Fixes to allow libbpf to be de-vendored</title>
<updated>2022-09-03T21:16:53+00:00</updated>
<author>
<name>Daniel Thompson</name>
<email>daniel@redfelineninja.org.uk</email>
</author>
<published>2022-05-19T09:23:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=3ef1d5c79985263436b3a240ea06375cbef7fcf3'/>
<id>urn:sha1:3ef1d5c79985263436b3a240ea06375cbef7fcf3</id>
<content type='text'>
De-vendoring libbpf resolves a SEGV everytime we run bpftrace.
Unfortunately it is not currently possible to de-vendor libbpf because
bcc does not build.

Fix this with brute force and ignorance... and in a seperate patch so
this can be treated as an explanation of the problem and ripped out in
favour of the right fix.

Signed-off-by: Daniel Thompson &lt;daniel.thompson@linaro.org&gt;
</content>
</entry>
<entry>
<title>bpftrace: Fix segfault when btf__type_by_id returns NULL</title>
<updated>2022-08-25T23:06:26+00:00</updated>
<author>
<name>Michal Wojcik</name>
<email>michal.wojcik@linaro.org</email>
</author>
<published>2022-08-25T14:58:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=da86f6c3a19d7c0cd1e99810ac2000dd1668ffac'/>
<id>urn:sha1:da86f6c3a19d7c0cd1e99810ac2000dd1668ffac</id>
<content type='text'>
Fixes segfault when running i.e. bpftrace -l

Signed-off-by: Michal Wojcik &lt;michal.wojcik@linaro.org&gt;
</content>
</entry>
<entry>
<title>bpftrace: Fix build with new libbpf</title>
<updated>2022-04-29T00:54:34+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2022-04-28T14:47:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=bb3e56b06f9d64d6f03b2e752b71690194d88a67'/>
<id>urn:sha1:bb3e56b06f9d64d6f03b2e752b71690194d88a67</id>
<content type='text'>
Fixes
git/src/btf.cpp:651:10: error: no matching function for call to 'btf_dump__new'

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>bcc: Enable riscv64 builds</title>
<updated>2022-03-06T16:30:36+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2022-03-06T07:15:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=5708f063e3a215535a1eb44af4f0e281dd1032d3'/>
<id>urn:sha1:5708f063e3a215535a1eb44af4f0e281dd1032d3</id>
<content type='text'>
Disable LuaJIT on rv64 since its not yes ported

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