[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2dcdc11c-4d04-4b0e-ddb7-04d969d04651@redhat.com>
Date: Fri, 15 Mar 2019 21:14:43 +0100
From: Ivan Vecera <ivecera@...hat.com>
To: Stanislav Fomichev <sdf@...ichev.me>
Cc: netdev@...r.kernel.org, Shuah Khan <shuah@...nel.org>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>,
"open list:BPF (Safe dynamic programs and tools)"
<bpf@...r.kernel.org>, open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next] selftests: bpf: modify urandom_read and link it
non-statically
On 15. 03. 19 21:08, Stanislav Fomichev wrote:
> On 03/15, Ivan Vecera wrote:
>> After some experiences I found that urandom_read does not need to be
>> linked statically. When the 'read' syscall call is moved to separate
>> non-inlined function then bpf_get_stackid() is able to find
>> the executable in stack trace and extract its build_id from it.
> But why? Do you have some problems with it being linked statically?
>
Dependency... you don't need to install static glibc to compile the bpf samples.
Shared libc is available everytime.
Ivan
Powered by blists - more mailing lists