public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/10822] procfs file created too late
Date: Wed, 21 Oct 2009 22:23:00 -0000	[thread overview]
Message-ID: <20091021222251.1450.qmail@sourceware.org> (raw)
In-Reply-To: <20091021211006.10822.dsmith@redhat.com>


------- Additional Comments From jistone at redhat dot com  2009-10-21 22:22 -------
While we are in our initialization phase, any probes that fire will quietly skip
their handlers.  We have a guarantee that begin probes will fire before any
others, so we can't run a procfs handler before then.  If you changed the
initialization order, then you might get your procfs file created sooner, but
reads/writes to it might be ignored.

This race between procfs creation and STAP_SESSION_RUNNING actually exists
regardless.  If we can't block users until RUNNING (instead of ignoring them),
then we probably need to wait to create the procfs in the first place.

As for the testcase, it could just use some other trigger than begin for the
first "advance" call.  Maybe a short timer probe would work, or even just run
the first echo as a "-c" command.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=10822

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  reply	other threads:[~2009-10-21 22:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-21 21:10 [Bug translator/10822] New: " dsmith at redhat dot com
2009-10-21 22:23 ` jistone at redhat dot com [this message]
2009-10-22  0:29 ` [Bug translator/10822] " fche at redhat dot com
2009-10-22 13:12 ` dsmith at redhat dot com
2009-10-22 13:26 ` dsmith at redhat dot com
2009-10-22 14:05 ` dsmith at redhat dot com

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=20091021222251.1450.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sources.redhat.com \
    /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).