This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug bpf/24358] 32-bit stapbpf: things need fixing re: (void *) use in libbpf and elsewhere
- From: "me at serhei dot io" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Mon, 18 Mar 2019 16:09:11 +0000
- Subject: [Bug bpf/24358] 32-bit stapbpf: things need fixing re: (void *) use in libbpf and elsewhere
- Auto-submitted: auto-generated
- References: <bug-24358-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24358
Serhei Makarov <me at serhei dot io> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|32-bit stapbpf: could not |32-bit stapbpf: things need
|find _stext in |fixing re: (void *) use in
|/proc/kallsyms |libbpf and elsewhere
--- Comment #1 from Serhei Makarov <me at serhei dot io> ---
In principle, we want to add 32-bit support. (Currently there is no 32-bit
Fedora bcc package either.)
The kallsyms parsing code in stapbpf.cxx had been hardcoded in a way that only
works on 64-bit architectures. This is an easy fix, but unmasks a whole range
of other issues that block stapbpf from working on 32-bit. Lots of code in
libbpf assumes void* is interchangeable with __u64, which leads to 'stack
smashing' errors on map read/write system calls.
Up to now, serious testing/qa for stapbpf has targeted x86_64, which is why
this issue came up only when I went to make serious transport changes and
decided these merited checking for regressions on other architectures.
--
You are receiving this mail because:
You are the assignee for the bug.