public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: przemoc@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.2-389-g8af0ed1 Date: Thu, 01 Jul 2010 11:55:00 -0000 [thread overview] Message-ID: <20100701115544.21314.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 8af0ed12bb050d38cb655eac6ca19efb9ff959d3 (commit) from 8cc799a5dece8e2358037a147458a5f9c3d9727a (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 8af0ed12bb050d38cb655eac6ca19efb9ff959d3 Author: Przemyslaw Pawelczyk <przemyslaw@pawelczyk.it> Date: Thu Jul 1 11:30:17 2010 +0200 Do not use relay_file_operations directly. Reference counting is important to avoid removing the module while the file exposing relay channel is being used. SystemTap alone does not need it, but malicious user may block reloading the module by opening such file and stap user won't notice it during unloading. relay_file_operations defined and exported in kernel/relay.c is const and .owner is obviously not set there, hence it shouldn't be used directly by any kernel module. Add relay_file_operations_w_owner and use it instead of mentioned one to fix 'trace' file handling w.r.t. module unloading. * runtime/transport/relay_v2.c: Add owner to the trace file. ----------------------------------------------------------------------- Summary of changes: runtime/transport/relay_v2.c | 8 +++++++- 1 files changed, 7 insertions(+), 1 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-07-01 11:55 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=20100701115544.21314.qmail@sourceware.org \ --to=przemoc@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).