From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/24358] 32-bit stapbpf: things need fixing re: (void *) use in libbpf and elsewhere
Date: Mon, 18 Mar 2019 16:09:00 -0000 [thread overview]
Message-ID: <bug-24358-6586-fhpX6PfZm1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <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.
prev parent reply other threads:[~2019-03-18 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 15:28 [Bug bpf/24358] New: 32-bit stapbpf: could not find _stext in /proc/kallsyms me at serhei dot io
2019-03-18 16:09 ` me at serhei dot io [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=bug-24358-6586-fhpX6PfZm1@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).