From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Netdev <netdev@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>
Cc: sdf@google.com, ast@kernel.org, Roman Gushchin <guro@fb.com>,
Song Liu <songliubraving@fb.com>
Subject: selftests/bpf/test_netcnt failed on i386 - ibbpf: failed to create map (name: 'percpu_netcnt'): Invalid argument
Date: Fri, 18 Jan 2019 13:39:24 +0530 [thread overview]
Message-ID: <CA+G9fYu-ku4dCOnUReot5jz3X18P1dWKiZCnnZaAJJt+p_HNjQ@mail.gmail.com> (raw)
Newly added test case bpf test_netcnt failed on i386 and qemu_i386 on
mainline and -next kernel.
Here we are running i386 kernel on x86_64 device.
Pass on x86_64, arm64 and arm.
Am i missing any pre required Kconfigs ?
Test output log,
selftests: bpf: test_netcnt
libbpf: failed to create map (name: 'percpu_netcnt'): Invalid argument
libbpf: failed to load object './netcnt_prog.o'
Failed to load bpf program
not ok 1.. selftests: bpf: test_netcnt [FAIL]
selftests: bpf_test_netcnt [FAIL]
Full test log,
https://lkft.validation.linaro.org/scheduler/job/574652#L2903
Kernel Config,
http://snapshots.linaro.org/openembedded/lkft/rocko/intel-core2-32/lkft/linux-mainline-ddiaz/52/config
Test results comparison of arm64, arm, x86_64 and i386 (kernel running
on x86_64 machine).
https://qa-reports.linaro.org/_/comparetest/?project=22&project=6&suite=kselftest&test=bpf_test_netcnt
Best regards
Naresh Kamboju
next reply other threads:[~2019-01-18 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 8:09 Naresh Kamboju [this message]
2019-01-19 1:47 ` selftests/bpf/test_netcnt failed on i386 - ibbpf: failed to create map (name: 'percpu_netcnt'): Invalid argument Roman Gushchin
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=CA+G9fYu-ku4dCOnUReot5jz3X18P1dWKiZCnnZaAJJt+p_HNjQ@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=ast@kernel.org \
--cc=guro@fb.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=songliubraving@fb.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;
as well as URLs for NNTP newsgroup(s).