This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/21998] New: receiving lots of "kbuild exited with status: 2" warnings when using tapset/linux/ip.stp
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Wed, 23 Aug 2017 20:41:02 +0000
- Subject: [Bug tapsets/21998] New: receiving lots of "kbuild exited with status: 2" warnings when using tapset/linux/ip.stp
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=21998
Bug ID: 21998
Summary: receiving lots of "kbuild exited with status: 2"
warnings when using tapset/linux/ip.stp
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: dsmith at redhat dot com
Target Milestone: ---
On 2.6.32-696.6.3.el6.i686 (but I believe this would happen on any RHEL6
system), I see the following:
====
# stap -v ../src.copy/testsuite/systemtap.base/ipaddr1.stp
Pass 1: parsed user script and 460 library scripts using
41700virt/27908res/2808shr/27304data kb, in 320usr/10sys/337real ms.
WARNING: kbuild exited with status: 2
WARNING: kbuild exited with status: 2
WARNING: kbuild exited with status: 2
WARNING: kbuild exited with status: 2
WARNING: kbuild exited with status: 2
WARNING: kbuild exited with status: 2
WARNING: kbuild exited with status: 2
WARNING: kbuild exited with status: 2
WARNING: kbuild exited with status: 2
WARNING: kbuild exited with status: 2
WARNING: kbuild exited with status: 2
WARNING: kbuild exited with status: 2
WARNING: kbuild exited with status: 2
WARNING: kbuild exited with status: 2
WARNING: kbuild exited with status: 2
Pass 2: analyzed script: 6 probes, 17 functions, 5 embeds, 7 globals using
101248virt/88652res/4072shr/86852data kb, in 3750usr/1760sys/6782real ms.
Pass 3: using cached
/root/.systemtap/cache/6b/stap_6bbe400a17c0b0dee4fb1670ccebacd3_25378.c
Pass 4: using cached
/root/.systemtap/cache/6b/stap_6bbe400a17c0b0dee4fb1670ccebacd3_25378.ko
Pass 5: starting run.
systemtap starting probe
systemtap ending probe
no packets seen
address errors = 0
bad family errors = 0
Pass 5: run completed in 10usr/10sys/21790real ms.
====
Those WARNINGs, besides being a bit annoying, are confusing the ipaddr.exp test
case (since that output wasn't expected).
Those warnings are coming from the following tapset function (along with a few
others):
====
function __ip_skb_saddr:long (iphdr)
{
return @choose_defined(@cast(iphdr, "iphdr", "kernel<linux/ip.h>")->saddr,
@cast(iphdr, "iphdr", "kernel<uapi/linux/ip.h>")->saddr)
}
====
The problem is that <uapi/linux/ip.h> doesn't exist on this system.
--
You are receiving this mail because:
You are the assignee for the bug.