To support building against v5.12+ and v5.13+ kernels, bumping to the
v2.12.6 lttng-release.
We drop the previously backported patches, and bring in the following
commits:
0d8e4ab9 Version 2.12.6
78f56ae3 fix: adjust ranges for RHEL 8.2 and 8.3
4c996ea7 Disable block rwbs bitwise enum in default build
4ac46085 Disable sched_switch bitwise enum in default build
5e22c27b Add experimental bitwise enum config option
937d307e Add defaults to Kconfig options
4a114d43 Sync `show_inode_state()` macro with upstream stable kernels
3bd6ac3e fix: block: remove disk_part_iter (v5.12)
8bbb8c9d Fix: Backport of "Fix: increment buffer offset when failing to copy from user-space"
30cddf69 Fix: increment buffer offset when failing to copy from user-space
4733b9ab Sync `show_inode_state()` macro with Ubuntu 4.15 kernel
ff21ec48 fix: mm, tracing: kfree event name mismatching with provider kmem (v5.12)
b2b02c29 Set 'stable-2.12' branch in git review config
00b42dbf fix backport: block: add a disk_uevent helper (v5.12)
771ff089 fix: Adjust ranges for Ubuntu 5.4.0-67 kernel
d8933959 fix: block: add a disk_uevent helper (v5.12)
71034df1 Fix: properly compare type enumeration
4d879d23 compiler warning cleanup: is_signed_type: compare -1 to 1
fead3a9c Fix: bytecode linker: validate event and field array/sequence encoding
92cc3e7f Fix: kretprobe: null ptr deref on session destroy
49c603ef fix: mm, tracing: record slab name for kmem_cache_free() (v5.12)
23a2f61f Fix: filter interpreter early-exits on uninitialized value
b3fdf78b Fix: memory leaks on event destroy
(From OE-Core rev: 4c2c3d3b84d883b2f1ad94095187e6b5b39e663f)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit c2f027b8e2f842915a0ffdfd6c2c0597f3b02bce)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a new lttng file to one of the tests to avoid test failures.
Also add a dependency on grep since standalone testing revealed test
failures without this. Normally this was added by other dependencies
in the ptest images so we didn't see this.
(From OE-Core rev: 379d198a4e11eae2cf5c2adb334a5dd4b9e8958a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 5799a807eed44d380e142913e50308589b9412ed)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add the following patches from stable-2.12 branch of lttng repository
to fix errors when building lttng-modules against 5.12+ kernel
since they are not present on the release 2.12.5:
- 17cd2dc9 fix: block: add a disk_uevent helper (v5.12)
- 127135b6 fix backport: block: add a disk_uevent helper (v5.12)
- 853d5903 fix: mm, tracing: kfree event name mismatching with
provider kmem (v5.12)
(From OE-Core rev: 86bcab9e9f4ee5e06f7db8c75d4b983fd2be59d2)
Signed-off-by: Vinicius Aquino <vinicius.aquino@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 2538ba2b3490e3599d9ccd637aa8486ea428f1b0)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are four changes in addition to the 2.12.5 release that we
need to build against the 5.12 kernel. Rather than only rely on
people knowing to use devupstream support to build against newer
kernels, we backport the 4 patches while waiting for release.
(From OE-Core rev: 2d45c09bfbad969549c719654f72714324299f00)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When building against kernel v5.12-rc+, we need extra changes
on top of the 2.12.5 release. We can bump devupstream separately
from the main release to grab those changes.
(From OE-Core rev: a53ddaa3dc5c072f9fbc5df5075e6067c0d6cc11)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a hack to hardcode in specific rpaths which we then remove,
allowing the build to be reproducible.
Strip build patches out of one of the test scripts too.
(From OE-Core rev: 18299a114c66280ba2d00becc3fae235d3a6cbd7)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
babeltrace2-ptest was referencing the host's python version in it's
makefiles. Whilst this could be fixed, its easier to correct the
python version being found to the target one which works much
more effectively and solves the issue.
(From OE-Core rev: 559f16d2fef4f8b04a9db1104b4a5b63f7876c68)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We'd appear to be past the need for a gcc7 patch from 3 years ago now.
(From OE-Core rev: 1ff0eb404819d259c411937bd12c82e04a5837ba)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
lttng-modules doesn't currently build against the lastest 5.10-rc
versions.
Upstream lttng does have fixes for the issues, but hasn't done a
release that contains them yet. There are other patches on the
2.12.x branch, but I've skipped them for now as they aren't
necessary for 5.10 builds, and can be picked up with the next
full update.
We also bump the dev-upstream hash to make them easier to pickup
for those building from git.
(From OE-Core rev: 47201e98bb293d59c5d41986d066fd7614b914fa)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Backporting the 10 patches since the lttng 2.12.2 release. We'll drop
them once .3 is released, but for now, we need the fixes to build
against the latest 5.4, 5.8 and 5.9 kernels.
We also bump the devupstream SRCREV to pickup the same changes.
(From OE-Core rev: 62c87d1a68c4f7c8f30c3c5330dcda9cbcbbbaa7)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating lttng-devupstream so we can build against kernel
5.9+
(From OE-Core rev: 11cf6562cf785d79da1f97257dcca93e75f37055)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some platforms support kernel tracing, some support userspace tracing.
This change:
* Moves the knowledge/config to one place in an inc file
* Allows lttng-tools to build without lttng-modules
* Hence enables tools+ust for riscv64
* Has the packagegroup just depend on lttng-tools which will pull in
ust/modules as needed
(From OE-Core rev: 1824cf062df928de65c1bff5e86e26b7b4d9d784)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since lttng-modules are not buildable, there is no point of building
tools either
(From OE-Core rev: 7138f09da4f3c523d4028fbe5b53923ad2b59a71)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Kernel 5.8+ and lttng requires kprobes and riscv64 lacks kprobes
Invert the COMPATIBLE_HOST regexp, as we support most of arches
(From OE-Core rev: 5a0096f3a2c268233c192deb455da67d2784afa4)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating to the 2.12.2 lttng-modules release. This is the standard
collection of bug fixes as well as changes to support building against
the v5.8 kernel.
Changelog follows:
2020-08-04 (National Chocolate Chip Cookie Day) LTTng modules 2.12.2
* Fix: Lock metadata cache on session destroy
* Fix: metadata stream leak, missing list removal and locking
* Fix: coherent state not changed atomically with metadata written
* fix: include module.h for EXPORT_SYMBOL_GPL
* fix: __lttng_vmalloc_node_range const caller introduced in v3.6
* fix: version range for overflow_callback
* fix: global_dirty_limit was introduced in v3.1
* fix: wrapper_uprobe_unregister is a void function
* fix: prior to v4.0, __vmalloc_node_range had no vm_flags param
* fix: vmalloc on v5.8 without KALLSYMS
* Detect missing symbols used with kallsyms_lookup at compile time
* Use exported symbol bdevname() instead of disk_name()
* Add git-review config
* fix: mm: remove vmalloc_sync_(un)mappings() (v5.8)
* fix: mm/writeback: discard NR_UNSTABLE_NFS, use NR_WRITEBACK (v5.8)
* fix: block: remove the error argument to the block_bio_complete (v5.8)
* fix: pipe_buf_operations rework (v5.8)
(From OE-Core rev: 08532e86d4c50e4d9ff99b4bb60f88ec3f5fc239)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To build against the v5.8-rc kernels, we need to pickup the latest
lttng-modules commits.
Bumping the devupstream version and SRCREV to do just that. Validated
against v5.8-rc4.
(From OE-Core rev: f743dfdb8f4b826bf64935720418cc30566b97ac)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Drop backports.
devupstream variant was incorrectly updated in a059fc67da
(changed to 2.12, but without updating SRCREV), so revert it back
to 2.11.2.
(From OE-Core rev: 64e27ce04c4acb68c946804627e5c594b73052cb)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upgrade lttng-tools 2.11.2 -> 2.12.0:
* drop x32 patch, as it was merged upstream
* update ptest file mi-lttng-3.0.xsd -> mi-lttng-4.0.xsd
* add local patch to fix ptest build failure on musl
* License-Update: licenses were moved under LICENSES directory and changed in
upstream commit [1]
[1] ab5be9fa2e
(From OE-Core rev: 62357f16ecc8368cf8a92290e973633622cd6368)
Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fix the following warnings introduced after backporting linux kernel commit [1]
to stable branches:
# lttng create session
...
[ 483.242037] LTTng: vmalloc_sync_all symbol lookup failed.
[ 483.257056] Page fault handler and NMI tracing might trigger faults.
...
These patches should be dropped when a new stable 12.0 release is available.
[1] 763802b53a
(From OE-Core rev: f2e48f9127aee949364696315e3adc861aba1dd6)
Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upgrade to version 2.11.2 in order to fix some build errors
with latest 5.4 kernel.
- conflicting types for 'trace_fast_page_fault'
Reproductible on kernel greater than v5.4.19, starting with commit
8a1cd01bee ("KVM: x86: Use gpa_t for cr2/gpa to fix TDP support on
32-bit KVM")
Error messages:
lttng-modules-2.11.1/probes/../probes/lttng-tracepoint-event-impl.h:130:6:
error:
130 | void trace_##_name(_proto);
tmp/work-shared/axxiax86-64/kernel-source/include/linux/tracepoint.h:233:21:
note: previous definition of 'trace_fast_page_fault' was here
233 | static inline void trace_##name(proto)
- conflicting types for 'trace_rcu_dyntick'
Reproductible on kernel greater than v5.4.22, starting with commit
6cf539a87a ("rcu: Fix data-race due to atomic_t copy-by-value")
Error messages:
lttng-modules-2.11.1/probes/../probes/lttng-tracepoint-event-impl.h:130:6:
error: conflicting types for 'trace_rcu_dyntick'
130 | void trace_##_name
tmp/work-shared/axxiax86-64/kernel-source/include/linux/tracepoint.h:233:21:
note: previous definition of 'trace_rcu_dyntick' was here
233 | static inline void trace_##name(proto)
(From OE-Core rev: 8fcc33aea08fc1e82818893feb7b01c7cc1e6416)
Signed-off-by: Daniel Dragomir <Daniel.Dragomir@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When add below line to local.conf to enable debug build:
DEBUG_BUILD = "1"
There comes below failure when run "bitbake babeltrace2"
| ../../../../../git/src/plugins/ctf/fs-src/fs.c: In function 'ds_index_insert_ds_index_entry_sorted':
| ../../../../../git/src/plugins/ctf/fs-src/fs.c:702:5: error: 'other_entry' may be used uninitialized in this function [-Werror=maybe-uninitialized]
| 702 | !ds_index_entries_equal(entry, other_entry)) {
So initialize the other_entry pointer to fix the above error.
(From OE-Core rev: 1b98db372a1fdaecf9bb897b0ee4b2e72af22f81)
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Babeltrace 1 vs. Babeltrace 2
The Babeltrace project exists since 2010. In 2020, Babeltrace 2 was released.
Babeltrace 2 is a complete rewrite of the library, Python bindings, and CLI. It
is plugin based and offers much more features and potential than Babeltrace 1.
Because Babeltrace 2 is still a young released project, some distributions still
provide packages for the Babeltrace 1 project. Both projects can coexist on the
same system as there are no common installed files.
(From OE-Core rev: be52889ba5e5a2cf02f50b3f3acee8ca72ec494d)
Signed-off-by: Anders Wallin <wallinux@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
version 2.x.x will be added with a new babeltrace2 recipe
(From OE-Core rev: 0616a5dbc61561fefcd1822ce263837437466df2)
Signed-off-by: Anders Wallin <wallinux@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upstream is aware, and will investigate and fix.
(From OE-Core rev: 96c286a1b2f9fc8e8bf4fb29ae62551a323af5c3)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
