This is the mail archive of the
systemtap-cvs@sourceware.org
mailing list for the systemtap project.
[SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-0.9-115-g436b47f
- From: jistone at sourceware dot org
- To: systemtap-cvs at sourceware dot org
- Date: 14 Mar 2009 00:08:15 -0000
- Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-0.9-115-g436b47f
- Reply-to: systemtap at sourceware dot org
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "systemtap: system-wide probe/trace tool".
The branch, master has been updated
via 436b47f678c2fc5397ed66a1eddf6b419cc6585b (commit)
from 52aeb26b8d83c26e00adaf70bbf5a3a828689fb2 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 436b47f678c2fc5397ed66a1eddf6b419cc6585b
Author: Josh Stone <jistone@redhat.com>
Date: Fri Mar 13 16:22:04 2009 -0700
Move lookup_bad_addr call in STAPCONF_PROBE_KERNEL
With most of the implementations, kread/kwrite call deref/store_deref,
and so it makes sense to have lookup_bad_addr in the latter as an
underlying address check.
However, in the STAPCONF_PROBE_KERNEL case that uses probe_kernel_read
and probe_kernel_write, the roles are reversed, so lookup_bad_addr needs
to be in kread/kwrite.
Also note that __deref_bad and __store_deref_bad should only be used in
cases that can be determined at compile time. These turn into invalid
symbols which prevent the module from loading. (They might be better
replaced with compile-time assertions.)
-----------------------------------------------------------------------
Summary of changes:
runtime/loc2c-runtime.h | 14 ++++++--------
1 files changed, 6 insertions(+), 8 deletions(-)
hooks/post-receive
--
systemtap: system-wide probe/trace tool