[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6E5513F5-0ACC-42C1-B6B2-0F73D3675859@redhat.com>
Date: Mon, 04 May 2020 10:57:06 +0200
From: "Eelco Chaudron" <echaudro@...hat.com>
To: "Andrii Nakryiko" <andrii.nakryiko@...il.com>
Cc: bpf <bpf@...r.kernel.org>, "David S. Miller" <davem@...emloft.net>,
Networking <netdev@...r.kernel.org>,
"Alexei Starovoitov" <ast@...nel.org>,
"Daniel Borkmann" <daniel@...earbox.net>,
"Martin Lau" <kafai@...com>, "Song Liu" <songliubraving@...com>,
"Yonghong Song" <yhs@...com>, "Andrii Nakryiko" <andriin@...com>,
"Toke Høiland-Jørgensen" <toke@...hat.com>
Subject: Re: [PATCH bpf-next] libbpf: fix probe code to return EPERM if
encountered
On 1 May 2020, at 21:16, Andrii Nakryiko wrote:
> On Fri, May 1, 2020 at 2:56 AM Eelco Chaudron <echaudro@...hat.com> wrote:
<SNIP>
>>
>> Let me know, and I sent out a v2.
>
> Yes, that's the split I had in mind, but I'd move
> bpf_object__probe_loading() call directly into bpf_object__load() to
> be the first thing to check. probe_caps() should still be non-failing
> if any feature is missing. Does it make sense?
I think I got it :) I’ll send out a v2 soon…
//Eelco
Powered by blists - more mailing lists