From: Daniel Borkmann <daniel@iogearbox.net>
To: "Nikita V. Shirokov" <tehnerd@tehnerd.com>,
Alexei Starovoitov <ast@kernel.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v2 bpf-next 1/1] libbpf: make bpf_object__open default to UNSPEC
Date: Fri, 23 Nov 2018 22:49:48 +0100 [thread overview]
Message-ID: <5a8c19bb-1e4a-e546-e75f-0f7a592b3d5b@iogearbox.net> (raw)
In-Reply-To: <20181123205812.2562-1-tehnerd@tehnerd.com>
On 11/23/2018 09:58 PM, Nikita V. Shirokov wrote:
> currently by default libbpf's bpf_object__open requires
> bpf's program to specify version in a code because of two things:
> 1) default prog type is set to KPROBE
> 2) KPROBE requires (in kernel/bpf/syscall.c) version to be specified
>
> in this patch i'm changing default prog type to UNSPEC and also changing
> requirments for version's section to be present in object file.
> now it would reflect what we have today in kernel
> (only KPROBE prog type requires for version to be explicitly set).
>
> v1 -> v2:
> - RFC tag has been dropped
>
> Signed-off-by: Nikita V. Shirokov <tehnerd@tehnerd.com>
Applied, thanks!
prev parent reply other threads:[~2018-11-24 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 20:58 [PATCH v2 bpf-next 1/1] libbpf: make bpf_object__open default to UNSPEC Nikita V. Shirokov
2018-11-23 21:49 ` Daniel Borkmann [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=5a8c19bb-1e4a-e546-e75f-0f7a592b3d5b@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tehnerd@tehnerd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox