From: David Smith <dsmith@redhat.com>
To: "systemtap@sourceware.org" <systemtap@sourceware.org>
Subject: draft release notes
Date: Mon, 21 Dec 2009 19:12:00 -0000 [thread overview]
Message-ID: <4B2FC888.3000002@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 294 bytes --]
Here are some draft release notes for the next systemtap release. Please
review them and let me know if you have suggestions for improvement or
if you see anything I've left out.
Thanks.
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)
[-- Attachment #2: release-1.XXX.txt --]
[-- Type: text/plain, Size: 7272 bytes --]
The SystemTap team announces release 1.XXX.
better support for gcc 4.5 richer DWARF debuginfo, new preprocessor
conditional for kernel 'CONFIG_*' testing, improved (experimental)
unprivileged user support, better local-vs-global variable warnings,
better return codes, bug fixes, and more...
= Where to get it
http://sourceware.org/systemtap/ - our project page
http://sourceware.org/systemtap/ftp/releases/systemtap-1.XXX.tar.gz
http://koji.fedoraproject.org/koji/packageinfo?packageID=615
git tag release-1.XXX (commit FIXME)
= How to build it
See the README and NEWS files at
http://sourceware.org/git/?p=systemtap.git;a=tree
Further information at http://sourceware.org/systemtap/wiki/
= SystemTap frontend (stap) changes
- Systemtap now warns about global variables being referenced from other
script files. This aims to protect against unintended local-vs-global
namespace collisions such as:
% cat some_tapset.stp
probe baz.one = bar { foo = $foo; bar = $bar }
% cat end_user_script.stp
global foo # intended to be private variable
probe timer.s(1) { foo ++ }
probe baz.* { println(foo, pp()) }
% stap end_user_script.stp
WARNING: cross-file global variable reference to foo from some_tapset.stp
- Better support for richer DWARF debuginfo output from GCC 4.5
(variable tracking assignments). Kernel modules are now always resolved
against all their dependencies to find any info referring to missing
symbols. DW_AT_const_value is now supported when no DW_AT_location
is available.
- Any output line that starts with "ERROR", as in error("foo"), will
promote a "Pass 5: run failed", and the return code is 1.
- The loading of signed modules by staprun is no longer allowed for
ordinary, unprivileged users. This means that only root, members of
the group 'stapdev' and members of the group 'stapusr' can load
systemtap modules using staprun, stap or stap-client. The minimum
privilege required to run arbitrary --unprivileged scripts is now
'stapusr' membership.
= SystemTap script language changes
- Preprocessor conditional for kernel configuration testing:
%( CONFIG_foo == "y" %? ... %)
= SystemTap tapset changes
- ftrace(msg:string) tapset function to send strings to the system-wide
ftrace ring-buffer (if any).
= New script examples
- interrupt/interrupts-by-dev.stp Tracks interrupts by device
- io/mbrwatch.stp Monitors MBR reads/writes
- memory/vm.tracepoints.stp Tracks memory slab/slub allocations
- network/tcp_trace.stp Tcp connection tracing utility
- process/plimit.stp Prints pid resource limits
- profiling/sched_switch.stp Display scheduler task switches
= Other notes
- The stap-server initscript is available. This initscript allows you
to start systemtap compile servers as a system service and to manage
these servers as a group or individually. The stap-server initscript
is installed by the systemtap-server rpm. The build directory for
the uprobes module (/usr/share/systemtap/runtime/uprobes) is made
writable by the 'stap-server' group. All of the files generated when
building the uprobes module, including the digital signature, are
also writable by members of stap-server.
See initscript/README.stap-server for details.
- When using the systemtap client and server udp port 5353 must be
open in your firewall in order for the clent to find servers using
avahi-browse.
- Some kernel crashes continue to be reported when a script probes
broad kernel function wildcards.
= Bugs fixed for this release
4037 make staprun 32/64-bit interoperable
4571 NFS tests missing from test suite
5150 buildok/nfs-all-probes.stp fails
5434 Error processing (missing) nfsservctl syscall
5872 Scsi tapset needs updation for 2.6.25-rc* kernels
5890 sys.stp fails on 2.6.25 x86_64
5916 Exploit kretprobe entry_handler + data pouch?
6979 loc2c code generation error
6991 accept system call missed on 2.6.27
9973 module signing for unprivileged users
10010 support $globals in shared libraries
10013 Support ENABLED sdt probe macro
10015 Possible uninitialized variable use in sym.c
10081 improve build-id mismatch message
10099 extend printf %M to support hexdumping large buffers
10231 Systemtap variable references fail on custom ppc64 kernels
10390 option to print into systemwide ftrace buffer
10466 stap -L misrepresents variables available to multi-probe aliases
10516 on rawhide, getting a warning about bad percpu allocation
10561 stap-server: take over signing duties, allow arg passing
10574 Some functions resolve to pc=0x0
10575 occasional stapio hangs for -c CMD
10593 Old gcc fails --with-elfutils configure
10595 uprobe probes causes selinux failures
10621 init.d script for systemtap-server
10622 unsuccessful location searches for extern $variables
10632 Random number generator for .stp
10644 forward-port staplog
10650 unprivileged embedded-c functions in tapset
10653 intermittent itrace crashes
10658 uprobes uproc->rwsem possible recursive locking detected
10678 vta-gcc: cannot find module nfs debuginfo
10700 log() doesn't output newline anymore
10702 preprocessor directive for kernel CONFIG_foo
10703 compilation error of ext4 tracepoint on 2.6.32
10706 line buffering needed in staprun?
10724 stap should not retry if there is a permissions error
10726 Getting wrong scope for inlined function
10746 utrace-less kernels generate funky errors
10750 translator permits excessively-vararged call into runtime
10761 pass staprun/stapio verbosity to final staprun -d
10799 global vs local variable confusion
10820 stap -L should take varaible location list into account
10822 procfs file created too late
10839 KRETACTIVE should have a smaller default value
10849 make MAXSKIPPED overflow trigger an error message
10854 Race between script startup and abnormal shutdown
10866 exit with rc != 0 on script ERRORs
10869 kretprobes waste a lot of memory on kretprobe_instances
10877 improve probe point error reporting
10923 frame_base given by DW_OP_call_frame_cfa in .debug_frame fail
10927 do-while statement unimplemented, but documented
10951 Process probes not in language reference manual
10974 testsuite/buildok/aux_syscalls-embedded.stp failure
10976 Untrusted uprobes.ko.sig shouldn't be fatal for the privileged
10981 buildok/netdev.stp failures on rhel5
10983 Power tracepoints use the wrong header in 2.6.32-rc7
10984 restrict unprivileged mode operation to "stapusr" or similar
11015 Support shared library reloading (in different processes)
11020 SIGUSR2 file switching doesn't work with busy script
11034 review context struct allocation mechanism
11089 process.mark() probes with same name trigger wrongly
11097 debug memory tracker shows memory overwrite in MAXNESTING
= Test results on various systems
- After running "sudo make installcheck" from the test suite, on a
suitably equipped machine (kernel debugging data and other stuff
installed), you should see 1000-1100 passes and a small handful of
failures.
next reply other threads:[~2009-12-21 19:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 19:12 David Smith [this message]
2009-12-22 22:03 ` Josh Stone
-- strict thread matches above, loose matches on Subject: below --
2009-06-11 1:45 Josh Stone
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=4B2FC888.3000002@redhat.com \
--to=dsmith@redhat.com \
--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).