* EPERM failures for repeated runs
@ 2019-10-22 14:36 Cyril Hrubis
0 siblings, 0 replies; only message in thread
From: Cyril Hrubis @ 2019-10-22 14:36 UTC (permalink / raw)
To: Alexei Starovoitov, Daniel Borkmann, Martin KaFai Lau, Song Liu,
Yonghong Song, David S. Miller, Jakub Kicinski,
Jesper Dangaard Brouer, John Fastabend
Cc: netdev, bpf, linux-kernel, ltp, Richard Palethorpe
Lately we started to write BPF testcases for LTP and after writing a
first few tests we found out that running more than a few in a row
causes them to fail with EPERM.
The culprit is deferred cleanup of the bpf maps that are locked in the
We worked around that by bumping the limit for the tests in:
But it looks like this value will not scale, especially for
architectures that have larger than 4k pages, running four BPF tests in
a row still fails on ppc64le even with the increased limit.
Perhaps I'm naive but can't we check, in the kernel, if there is
deferred cleanup in progress if we fail to lock memory for a map and
retry once it's done?
Or is this intended behavior and should we retry on EPERM in userspace?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-10-22 14:36 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-22 14:36 EPERM failures for repeated runs Cyril Hrubis
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).