public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/18944] New: the ioblock.stp tapset fails to compile on RHEL7
Date: Wed, 09 Sep 2015 20:35:00 -0000	[thread overview]
Message-ID: <bug-18944-6586@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=18944

            Bug ID: 18944
           Summary: the ioblock.stp tapset fails to compile on RHEL7
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: dsmith at redhat dot com
  Target Milestone: ---

On rhel7 (3.10.0-305.el7.x86_64), the buildok testsuite gets 3 failures from
the ioblock tapset:

FAIL: buildok/ioblock-all-probes.stp
FAIL: buildok/ioblock-detailed.stp
FAIL: buildok/ioblock-embedded.stp

The errors are all the same:

====
Running ../../src/testsuite/buildok/ioblock-all-probes.stp
starting ../../src/testsuite/buildok/ioblock-all-probes.stp
spawn1 stap -wp4 ../../src/testsuite/buildok/ioblock-all-probes.stp
spawn stap -wp4 ../../src/testsuite/buildok/ioblock-all-probes.stp^M
/tmp/stap5pFzCi/stap_1a6f9b48025b6d740d13db61b520d558_2603_src.c:38:0: error:
"REQ_WRITE" redefined [-Werror]^M
 #define REQ_WRITE               (1 << BIO_RW)^M
 ^^M
In file included from include/linux/fs.h:29:0,^M
                 from include/linux/ftrace.h:18,^M
                 from include/linux/kprobes.h:42,^M
                 from /usr/local/share/systemtap/runtime/linux/runtime.h:21,^M
                 from /usr/local/share/systemtap/runtime/runtime.h:24,^M
                 from
/tmp/stap5pFzCi/stap_1a6f9b48025b6d740d13db61b520d558_2603_src.c:25:^M
include/linux/blk_types.h:212:0: note: this is the location of the previous
definition^M
 #define REQ_WRITE  (1ULL << __REQ_WRITE)^M
 ^^M
cc1: all warnings being treated as errors^M
make[4]: *** [/tmp/stap5pFzCi/stap_1a6f9b48025b6d740d13db61b520d558_2603_src.o]
Error 1^M
make[3]: *** [_module_/tmp/stap5pFzCi] Error 2^M
WARNING: kbuild exited with status: 2^M
Pass 4: compilation failed.  [man error::pass4]^M
====

What's odd here is that the ioblock tapset has code to deal with this:

====
%{
#include <linux/bio.h>
#include <linux/genhd.h>
#ifdef STAPCONF_BLK_TYPES
#include <linux/blk_types.h>
#else
#define REQ_WRITE               (1 << BIO_RW)
#endif
%}
====

STAPCONF_BLK_TYPES is supposed to get defined by one of our "autoconf" like
tests when linux/blk_types.h is present and usable in the kernel source.

However, when this autoconf test is run, we get this error:

====
In file included from
/usr/local/share/systemtap/runtime/linux/autoconf-blk-types.c:1:0:
include/linux/blk_types.h:113:2: error: expected specifier-qualifier-list
before ‘RH_KABI_REPLACE’
  RH_KABI_REPLACE(void *rh_reserved1, struct bio_aux *bio_aux)
  ^
====

So, blk_types.h is present, but uses a Red Hat-only macro that comes from
/usr/src/kernel/KVER/include/linux/rh_kabi.h. In a more perfect work
blk_types.h would have included this file itself.

We'll need to rework the runtime/linux/autoconf-blk-types.c file to handle
this.

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

             reply	other threads:[~2015-09-09 20:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-09 20:35 dsmith at redhat dot com [this message]
2015-09-14 15:39 ` [Bug runtime/18944] " 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-18944-6586@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).