From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] systemtap: upgrade 4.5 -> 4.6
Date: Mon, 22 Nov 2021 22:59:33 +0800 [thread overview]
Message-ID: <1637593174-99263-2-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1637593174-99263-1-git-send-email-wangmy@fujitsu.com>
support for 64-bit RISC-V architecture, liveness analysis for guru-mode write operations,
bpf syscall_any and abort() tapsets, bpf foreach iteration of multi-key arrays,
return of inter-cpu output ordering
Changelog is as follows:
= SystemTap frontend (stap) changes
- stap-prep now tries to download the main kernel debuginfo file from
a debuginfod server, if configured.
= SystemTap backend changes
- SystemTap has added support for the 64-bit RISC-V architecture.
- SystemTap now uses DynInst to perform a liveness analysis on
target variables and warn when a guru-mode modification to a variable
will have no effect. The liveness analysis is currently done on
x86_64, PowerPC, and AArch64.
- The kernel-user relayfs transport again sorts messages into a total
time order across CPUs. High output-volume scripts may need a
larger "-s BUF" parameter to reliably transfer. "-b" bulk mode
is also available again as an alternative.
- The bpf backend now supports foreach iteration in multi-key associative arrays.
= SystemTap tapset changes
- Updated syscall_any tapset mapping to include newer syscalls.
- syscall_any tapset can be used by the bpf backend.
- abort() tapset can be used by the bpf backend.
= Known issues with this release
- There are known issues on kernel 5.10+ after adapting to set_fs()
removal, with some memory accesses that previously returned valid data
instead returning -EFAULT (see PR26811).
- An sdt probe cannot parse a parameter that uses a segment register.
(PR13429)
- The presence of a line such as
*CFLAGS += $(call cc-option, -fno-var-tracking-assignments)
in older linux kernel Makefile unnecessarily reduces debuginfo quality,
consider removing that line if you build kernels. Linux 5.10+ fixes this.
= Bugs fixed for this release <https://sourceware.org/PR#####>
6562 $SYSTEMTAP_DEBUGINFO_PATH does not work
15724 stapdyn looking for libdyninstAPI_RT.a
26839 Systemtap build failures with clang
27820 abort() tapset not implemented in the bpf mode
27829 support for floating point values passed through sdt.h markers
27864 loc2stap.cxx assertion failure on loc_unavailable type location, rawhide
27881 failed to extend vma mapped entry when the address is adjacent
27903 handle f33 glibc $$parms
27932 List Python as a prerequisite in README
27933 Use of unitialized functioncall synthetic field in
27934 failure to attach statement
27940 The /* pc=0x... */ is no longer printed by "stap -v -L 'kernel.function("*")'
27942 testsuite/systemtap.base/perf.sh drop bashism
27984 stap skipping partially-inlined instance, but it is not inline function actually
28070 extend vma end address to the different module
28079 adapt to kernel 5.14 task_struct.__state change
28084 autoconf-x86-uniregs.c compile failled with -Werror cause STAPCONF_X86_UNIREGS missing
28140 kernel panic on tracepoint activation in stap module
28184 task_fd_lookup failed on linux 5.11
28244 linux objtool imposes symbol length limits on generated function names
28384 finish nfs_proc tapset port 4.3 string server_ip
28443 Provide syscall_any tapset for bpf
28449 loss of cross-cpu output ordering
28544 procfs_bpf.exp regression due to string handling error
28557 module kprobe insertion on modern kernels
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
meta/recipes-kernel/systemtap/systemtap_git.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-kernel/systemtap/systemtap_git.inc b/meta/recipes-kernel/systemtap/systemtap_git.inc
index 25546f7cb2..22b07f1516 100644
--- a/meta/recipes-kernel/systemtap/systemtap_git.inc
+++ b/meta/recipes-kernel/systemtap/systemtap_git.inc
@@ -1,7 +1,7 @@
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
-SRCREV = "7f6992539fb22c93c21ac30c94508bf655d496a7"
-PV = "4.5"
+SRCREV = "2e9f2f6967e44ce2bf8f34932b5bdd738ece2161"
+PV = "4.6"
SRC_URI = "git://sourceware.org/git/systemtap.git;branch=master \
file://0001-Do-not-let-configure-write-a-python-location-into-th.patch \
--
2.25.1
next prev parent reply other threads:[~2021-11-22 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 14:59 [OE-core] [PATCH] stress-ng: upgrade 0.13.06 -> 0.13.07 Wang Mingyu
2021-11-22 14:59 ` Wang Mingyu [this message]
2021-11-22 15:02 ` [OE-core] [PATCH] systemtap: upgrade 4.5 -> 4.6 Alexander Kanavin
2021-11-22 14:59 ` [OE-core] [PATCH] python3-scons: upgrade 4.2.0 -> 4.3.0 Wang Mingyu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1637593174-99263-2-git-send-email-wangmy@fujitsu.com \
--to=wangmy@fujitsu.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.