From: Stefan Wahren <stefan.wahren@i2se.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Shubham Bansal <illusionist.neo@gmail.com>,
bpf@vger.kernel.org, jpalus@fastmail.com,
regressions@lists.linux.dev,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [BUG] null pointer dereference when loading bpf_preload on Raspberry Pi
Date: Mon, 13 Jun 2022 16:42:33 +0200 [thread overview]
Message-ID: <de4da55b-a074-b375-c41d-413bb19a428b@i2se.com> (raw)
In-Reply-To: <YqcbgmTmezGM0VPr@shell.armlinux.org.uk>
Hi,
Am 13.06.22 um 13:12 schrieb Russell King (Oracle):
> On Mon, Jun 13, 2022 at 12:22:47AM +0200, Stefan Wahren wrote:
>> It would be nice to get a hint, how to narrow down or which commit might
>> trigger this issue.
> The standard way? git bisect?
>
> So it happens on 5.18.0 and 5.18.3. Presumably it didn't happen with
> 5.17?
in 5.17 there is a libelf dependency (was removed in 5.18), which cause
a compile issue about missing libelf.h which is only available on my
host system but not available in my Linaro cross toolchain.
Should i copy the libelf.h somewhere, so the cross compiler finds it?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-13 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 22:22 [BUG] null pointer dereference when loading bpf_preload on Raspberry Pi Stefan Wahren
2022-06-13 11:12 ` Russell King (Oracle)
2022-06-13 14:42 ` Stefan Wahren [this message]
2022-06-15 6:11 ` Stefan Wahren
2022-06-15 8:31 ` Peter Robinson
2022-06-15 9:57 ` Stefan Wahren
2022-06-15 10:07 ` Peter Robinson
2022-06-19 17:06 ` Thorsten Leemhuis
2022-09-03 14:17 ` Stefan Wahren
2022-09-03 14:44 ` Stefan Wahren
2022-09-04 9:28 ` Thorsten Leemhuis
2022-07-04 12:42 ` Thorsten Leemhuis
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=de4da55b-a074-b375-c41d-413bb19a428b@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=illusionist.neo@gmail.com \
--cc=jpalus@fastmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=regressions@lists.linux.dev \
/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 NNTP newsgroup(s).