From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/15775] relay host/guest functionality is broken on RHEL6
Date: Mon, 22 Feb 2016 19:31:00 -0000 [thread overview]
Message-ID: <bug-15775-6586-sjPUIiYGDw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15775-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15775
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WONTFIX |---
--- Comment #2 from David Smith <dsmith at redhat dot com> ---
Note that the relay host/guest functionality also doesn't work on RHEL6, RHEL7
or any current fedora or rawhide kernels. The only place this works is on
RHEL5-era kernels.
Perhaps we should just deprecate this functionality (and remove its
documentation from the manpage)?
The least thing we could do here would be to change the sharedbuf.exp test case
to issue KFAILS (and reference this bug report).
(One *ugly* solution here would be to bypass the module exporting mechanism
here and use kallsyms_lookup_name() to find the function. The problem with this
approach is that wouldn't update the relay host module's reference count,
making it possible to remove the relay host module before the relay guest
module. We might be able to update the relay host module's reference count
ourselves but we don't really know the module's name and there are probably
several time-of-check-to-time-of-use (TOCTTOU) problems lurking there.)
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-02-22 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 19:02 [Bug runtime/15775] New: " dsmith at redhat dot com
2015-05-19 14:39 ` [Bug runtime/15775] " fche at redhat dot com
2016-02-22 19:31 ` dsmith at redhat dot com [this message]
2016-02-23 19:01 ` 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=bug-15775-6586-sjPUIiYGDw@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).