From: Tal Lossos <tallossos@gmail.com>
To: bpf <bpf@vger.kernel.org>
Cc: andrii@kernel.org, assaf.shab@gmail.com
Subject: Question regarding "BPF CO-RE reference guide" blog post
Date: Mon, 25 Oct 2021 15:05:48 +0300 [thread overview]
Message-ID: <CAO15rP=JzzanBC7Hj=9pshpMeWGJVpbt0wCiZfP8HwBaEbcFMw@mail.gmail.com> (raw)
Hello!
After reading Andrii's new blog post regarding BPF CO-RE, which was
really lovely and well written, I came up with a small question:
When you gave the example for BPF_CORE_READ, you've accessed the
executable pointer under linux_binfmt struct.
Is it a mistake with linux_binprm struct? or maybe I'm missing something.
Another thing, maybe you could add a little explanation about how
libbpf validates the structs offsets with the help of BTF? It's a key
part of CO-RE so it would be nice to have a little deep-dive in the
blog post about it :)
Thanks.
next reply other threads:[~2021-10-25 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 12:05 Tal Lossos [this message]
2021-10-25 19:20 ` Question regarding "BPF CO-RE reference guide" blog post 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='CAO15rP=JzzanBC7Hj=9pshpMeWGJVpbt0wCiZfP8HwBaEbcFMw@mail.gmail.com' \
--to=tallossos@gmail.com \
--cc=andrii@kernel.org \
--cc=assaf.shab@gmail.com \
--cc=bpf@vger.kernel.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 NNTP newsgroup(s).