From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/17393] java.exp: ERROR: Cannot attach to module control channel
Date: Mon, 21 Mar 2016 22:13:00 -0000 [thread overview]
Message-ID: <bug-17393-6586-1ovwGmw1ri@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17393-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17393
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from David Smith <dsmith at redhat dot com> ---
It looks like what is going on here is that the java support code adds
synthetic begin and end probes that install and delete the java probes. When
the end probe happens, the system() function is run to delete the java probes.
Unfortunately, the control channel and relayfs file descriptors are passed down
to the child process, and if it is still running when the module tries to exit,
removing the module will fail. If the control channel is still open, you'll get
EAGAIN. If the relayfs file descriptors are still open, you'll get EBUSY.
Fixed in commit 9010bbb by making sure all file descriptors are closed when
needed and marked close-on-exec.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2016-03-21 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 12:34 [Bug runtime/17393] New: " mcermak at redhat dot com
2014-09-15 13:37 ` [Bug runtime/17393] " mcermak at redhat dot com
2014-09-15 13:41 ` mcermak at redhat dot com
2016-03-08 15:52 ` dsmith at redhat dot com
2016-03-08 22:36 ` dsmith at redhat dot com
2016-03-21 22:13 ` dsmith at redhat dot com [this message]
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=bug-17393-6586-1ovwGmw1ri@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@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).