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-1.3-37-ga575167
Date: Fri, 06 Aug 2010 18:01:00 -0000	[thread overview]
Message-ID: <20100806180157.23823.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  a5751672ae06f66a5ce28efab17e406af535adfa (commit)
      from  116bd66960dfbba97a123c4f1fe903d717d1e805 (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 a5751672ae06f66a5ce28efab17e406af535adfa
Author: Josh Stone <jistone@redhat.com>
Date:   Fri Aug 6 10:55:32 2010 -0700

    Ignore empty files in the cache
    
    Sometimes crashes can leave just-written files at zero length, so we
    should be a little paranoid that our cached files are ok.  The stapconf
    header is especially vulnerable, as it will prevent all scripts from
    being compiled if it gets bad.
    
    * util.cxx (get_file_size(int)): Read the size from a file descriptor.
    * cache.cxx (get_stapconf_from_cache, get_script_from_cache): Check that
      cached files are non-empty before using them.

-----------------------------------------------------------------------

Summary of changes:
 cache.cxx |    9 ++++++---
 util.cxx  |   12 ++++++++++++
 util.h    |    1 +
 3 files changed, 19 insertions(+), 3 deletions(-)


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2010-08-06 18:01 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=20100806180157.23823.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).