public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Serhei Makarov" <me@serhei.io>
To: systemtap@sourceware.org
Cc: linux-kernel@vger.kernel.org, lwn@lwn.net
Subject: systemtap release 4.6
Date: Mon, 15 Nov 2021 16:36:04 -0500	[thread overview]
Message-ID: <2188aa33-9ca2-497a-a9fd-4af28dfe250e@www.fastmail.com> (raw)
In-Reply-To: <2587f978-3619-4ed7-ac31-1cb0c0d29b31@www.fastmail.com>

The SystemTap team announces release 4.6

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

= Where to get it

  https://sourceware.org/systemtap/ - our project page
  https://sourceware.org/systemtap/ftp/releases/
  https://koji.fedoraproject.org/koji/packageinfo?packageID=615
  git tag release-4.6 (commit 2e9f2f6967e44ce2bf8f34932b5bdd738ece2161)

  There have been over 149 commits since the last release.
  There have been 25 bugs fixed / features added since the last release.

= 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.

= SystemTap sample scripts

- All 190+ examples can be found at https://sourceware.org/systemtap/examples/

- New sample scripts:

   io/traceaio.stp
   Trace calls to io_submit, logging iocbs and iovecs.

- The stopwatch.stp sample script is now confirmed to work with the BPF backend:

= Examples of tested kernel versions 

  2.6.32 (RHEL6 i686, x86_64)
  3.10.0 (RHEL7 x86_64)
  4.15.0 (Ubuntu 18.04 x86_64)
  4.18.0 (RHEL8 x86_64, aarch64, ppc64le, s390x)
  5.14.14 (Fedora 35 x86_64)
  5.14.16 (Fedora 34 x86_64)
  5.15.0-rc7  (Fedora rawhide x86_64)

= 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.

= Contributors for this release

Aaron Merey, Alexandra Hájková*, Di Chen*, Du Zhe*, Frank Ch. Eigler
Junlong Li*, Nir Soffer*, Serhei Makarov, Sevan Janiyan*, Stan Cox
Sultan Alsawaf, Timm Bäder*, William Cohen

Special thanks to new contributors, marked with '*' above.

= 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

      reply	other threads:[~2021-11-15 21:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-08  2:02 systemtap release 4.5 Serhei Makarov
2021-11-15 21:36 ` Serhei Makarov [this message]

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=2188aa33-9ca2-497a-a9fd-4af28dfe250e@www.fastmail.com \
    --to=me@serhei.io \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=systemtap@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).