public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: jistone@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-0.9-115-g436b47f
Date: Sat, 14 Mar 2009 00:08:00 -0000	[thread overview]
Message-ID: <20090314000815.2493.qmail@sourceware.org> (raw)

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


                 reply	other threads:[~2009-03-14  0:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20090314000815.2493.qmail@sourceware.org \
    --to=jistone@sourceware.org \
    --cc=systemtap-cvs@sourceware.org \
    --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).