From: David Smith <dsmith@redhat.com>
To: William Cohen <wcohen@redhat.com>, systemtap@sourceware.org
Cc: Dave Long <dave.long@linaro.org>, Pratyush Anand <panand@redhat.com>
Subject: Re: Recent aarch64 kprobes and uprobes patch systemtap testing
Date: Fri, 11 Dec 2015 17:23:00 -0000 [thread overview]
Message-ID: <566B06A0.1020705@redhat.com> (raw)
In-Reply-To: <5669DF98.3030601@redhat.com>
On 12/10/2015 02:24 PM, William Cohen wrote:
> Hi All,
>
> Dave Long and Pratyush Anand have been working on kprobe and uprobe patches for aarch64. I have built a local version the uprobe/upstream_arm64_devel branch of https://github.com/pratyushanand/linux which includes those patches in a linux-4.4.0-rc3 kernel.
>
> The tests seemed to run fairly well and the results have been uploaded to dejazilla:
>
> https://web.elastic.org/~dejazilla/viewsummary.php?summary=%3D%27%3C56698DCC.3090207%40redhat.com%3E%27
... stuff deleted ...
> Also a number of network tests failed like the following
>
> TEST PWD=/root/systemtap_write/systemtap/testsuite/systemtap.examples/network
> meta taglines 'test_check: stap -g -p4 netfilter_drop.stp TCP 1' tag 'test_check' value 'stap -g -p4 netfilter_drop.stp TCP 1'
> attempting command stap -g -p4 netfilter_drop.stp TCP 1
> OUT /tmp/stapbIEqFl/stap_0c0db8521e3ea3b2d26dcde208a77baf_21082_src.c:2731:1: error: initialization from incompatible pointer type [-Werror]
> .hook = enter_netfilter_probe_0,
> ^
> /tmp/stapbIEqFl/stap_0c0db8521e3ea3b2d26dcde208a77baf_21082_src.c:2731:1: error: (near initialization for 'netfilter_opts_0.hook') [-Werror]
> /tmp/stapbIEqFl/stap_0c0db8521e3ea3b2d26dcde208a77baf_21082_src.c:2732:1: error: unknown field 'owner' specified in initializer
> .owner = THIS_MODULE,
> ^
> /tmp/stapbIEqFl/stap_0c0db8521e3ea3b2d26dcde208a77baf_21082_src.c:2732:1: error: initialization from incompatible pointer type [-Werror]
> /tmp/stapbIEqFl/stap_0c0db8521e3ea3b2d26dcde208a77baf_21082_src.c:2732:1: error: (near initialization for 'netfilter_opts_0.dev') [-Werror]
> cc1: all warnings being treated as errors
> make[4]: *** [/tmp/stapbIEqFl/stap_0c0db8521e3ea3b2d26dcde208a77baf_21082_src.o] Error 1
> make[3]: *** [_module_/tmp/stapbIEqFl] Error 2
> WARNING: kbuild exited with status: 2
> Pass 4: compilation failed. [man error::pass4]
This appears to be a problem with 4.4 kernels in general, not just an
aarch64 problem. It also happens on rawhide x86_64. It appears that the
kernel has had some changes in the area of netfilter probes.
I filed PR19358 on this issue.
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)
prev parent reply other threads:[~2015-12-11 17:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 20:24 William Cohen
2015-12-10 21:12 ` David Long
2015-12-11 4:19 ` Pratyush Anand
2015-12-11 4:43 ` David Long
2015-12-11 17:02 ` William Cohen
2015-12-16 5:22 ` Pratyush Anand
2015-12-16 13:14 ` William Cohen
2015-12-17 0:53 ` Pratyush Anand
2015-12-11 20:59 ` William Cohen
2015-12-16 11:55 ` Pratyush Anand
2015-12-16 13:10 ` William Cohen
2015-12-10 21:17 ` David Long
2015-12-11 17:23 ` David Smith [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=566B06A0.1020705@redhat.com \
--to=dsmith@redhat.com \
--cc=dave.long@linaro.org \
--cc=panand@redhat.com \
--cc=systemtap@sourceware.org \
--cc=wcohen@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).