public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: dsmith@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.3-343-gcf172f1 Date: Thu, 02 Dec 2010 20:06:00 -0000 [thread overview] Message-ID: <20101202200612.2773.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 cf172f14c8caf916965a05e34b2e42bf9a92b469 (commit) from d0d71073a908c337968247b53cd60833d9652b1a (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 cf172f14c8caf916965a05e34b2e42bf9a92b469 Author: David Smith <dsmith@redhat.com> Date: Thu Dec 2 14:05:39 2010 -0600 Fixed possible string buffer overruns in several embedded-C functions. * tapset/socket.stp (sock_flags_num2str): Use strlcat() instead of strcat() to guard against buffer overruns. Instead of creating the string in a temporary variable and then copying it to THIS->__retvalue, just create the string in THIS->__retvalue. (msg_flags_num2str): Ditto. * tapset/inet_sock.stp (daddr_to_string): Use snprintf() instead of sprintf() to guard against buffer overruns. * tapset/signal.stp (sigset_mask_str): Ditto. * tapset/s390/nd_syscalls.stp (get_32mmap_args): Use strlcat()/snprintf() instead of strcat()/sprintf() to guard against buffer overruns. * tapset/s390/syscalls.stp: Removed unused function get_32mmap_args(). * tapset/aux_syscalls.stp: Minor string-related fixes. * tapset/string.stp: Ditto. ----------------------------------------------------------------------- Summary of changes: tapset/aux_syscalls.stp | 25 +++++++++---- tapset/inet_sock.stp | 2 +- tapset/s390/nd_syscalls.stp | 62 ++++++++++++++++++--------------- tapset/s390/syscalls.stp | 58 ------------------------------- tapset/signal.stp | 4 ++- tapset/socket.stp | 80 +++++++++++++++++++++++++------------------ tapset/string.stp | 1 + 7 files changed, 103 insertions(+), 129 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-12-02 20:06 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=20101202200612.2773.qmail@sourceware.org \ --to=dsmith@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: linkBe 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).