From: John Fastabend <john.fastabend@gmail.com>
To: Owayss Kabtoul <owayssk@gmail.com>, bpf@vger.kernel.org
Subject: RE: Fwd: bpf syscall failing on aarch64 with "Invalid argument" (Asahi Linux on M1)
Date: Thu, 29 Sep 2022 19:11:05 -0700 [thread overview]
Message-ID: <63365039486df_233df208aa@john.notmuch> (raw)
In-Reply-To: <CAP-Vjpzqw=_t61tyJ7SPCLHresuX7XXv2gyQgO8NW1p5dNsViQ@mail.gmail.com>
Owayss Kabtoul wrote:
> Hello.
>
> I have built libbpf from source (a7c0f7e). When running any of the
> provided examples, the bpf syscall fails with "Invalid argument":
>
> ```
> $ sudo strace ./minimal
Could you post the minimal C code. Its likely easier to read than
trying to parse the strace output. Sure we could probably figure
it out from strace but lets go the easier route.
Caveat I didn't bother to try and read the strace.
Thanks,
John
next prev parent reply other threads:[~2022-09-30 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP-VjpyJxPNJ0438FbxEWxNbyL7zsCFwrEt6Tzw-vHz0ZQHxmg@mail.gmail.com>
2022-09-28 18:30 ` Fwd: bpf syscall failing on aarch64 with "Invalid argument" (Asahi Linux on M1) Owayss Kabtoul
2022-09-30 2:11 ` John Fastabend [this message]
2022-09-30 7:53 ` Owayss Kabtoul
2022-09-30 22:14 ` Andrii Nakryiko
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=63365039486df_233df208aa@john.notmuch \
--to=john.fastabend@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=owayssk@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.