From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Yonghong Song <yhs@fb.com>
Cc: ast@fb.com, daniel@iogearbox.net, guro@fb.com,
netdev@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH bpf-next] tools/bpf: adjust rlimit RLIMIT_MEMLOCK for test_dev_cgroup
Date: Wed, 20 Dec 2017 19:21:41 -0800 [thread overview]
Message-ID: <20171221032139.i3he3hus2noc2lkl@ast-mbp> (raw)
In-Reply-To: <20171220183708.2334406-1-yhs@fb.com>
On Wed, Dec 20, 2017 at 10:37:08AM -0800, Yonghong Song wrote:
> The default rlimit RLIMIT_MEMLOCK is 64KB. In certain cases,
> e.g. in a test machine mimicking our production system, this test may
> fail due to unable to charge the required memory for prog load:
>
> $ ./test_dev_cgroup
> libbpf: load bpf program failed: Operation not permitted
> libbpf: failed to load program 'cgroup/dev'
> libbpf: failed to load object './dev_cgroup.o'
> Failed to load DEV_CGROUP program
> ...
>
> Changing the default rlimit RLIMIT_MEMLOCK to unlimited
> makes the test pass.
>
> This patch also fixed a problem where when bpf_prog_load fails,
> cleanup_cgroup_environment() should not be called since
> setup_cgroup_environment() has not been invoked. Otherwise,
> the following confusing message will appear:
> ...
> (/home/yhs/local/linux/tools/testing/selftests/bpf/cgroup_helpers.c:95:
> errno: No such file or directory) Opening Cgroup Procs: /mnt/cgroup.procs
> ...
>
> Signed-off-by: Yonghong Song <yhs@fb.com>
Applied, Thanks Yonghong.
prev parent reply other threads:[~2017-12-21 3:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 18:37 [PATCH bpf-next] tools/bpf: adjust rlimit RLIMIT_MEMLOCK for test_dev_cgroup Yonghong Song
2017-12-21 3:21 ` Alexei Starovoitov [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=20171221032139.i3he3hus2noc2lkl@ast-mbp \
--to=alexei.starovoitov@gmail.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=guro@fb.com \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=yhs@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