From: Kees Cook <keescook@chromium.org>
To: Liu Yiding <liuyd.fnst@cn.fujitsu.com>
Cc: linux-kselftest@vger.kernel.org,
Prabhakar Kushwaha <prabhakar.pkin@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [Bug report] "make run_tests -C bpf" hanging forever
Date: Fri, 18 Oct 2019 09:21:37 -0700 [thread overview]
Message-ID: <201910180919.B3D3618@keescook> (raw)
In-Reply-To: <d08b43ee-6a21-c9aa-ea7b-9465ecbad772@cn.fujitsu.com>
On Fri, Oct 18, 2019 at 02:32:15PM +0800, Liu Yiding wrote:
> Hi All.
>
> The patch 5c069b6dedef "selftests: Move test output to diagnostic lines"
> from Apr 24, 2019,
>
> leads to `make run_tests -C bpf` hanging forever.
I can't even run this, the autodetection seems broken. I have BPF and
libelf installed....
$ make run_tests -C bpf
[...]
Auto-detecting system features:
... libelf: [ OFF ]
... bpf: [ OFF ]
Auto-detecting system features:
... libelf: [ OFF ]
... bpf: [ OFF ]
No libelf found
Makefile:269: recipe for target 'elfdep' failed
make[2]: *** [elfdep] Error 1
Makefile:154: recipe for target 'all' failed
make[1]: *** [all] Error 2
> Bpf includes many subtest, when cmd `make run_tests -C bpf` runs to
> test_lwt_seg6local.sh, task will hang and runner.sh never run next task. I
> checked ps aux, prefix.pl will never exit.
>
> ```
>
> 91058 [ 811.451584] # [25] VAR __license type_id=24 linkage=1
> 91059 [ 811.451586]-
> 91060 [ 811.455365] # [26] DATASEC license size=0 vlen=1 size == 0
> 91061 [ 811.455367]-
> 91062 [ 811.457424] #-
> 91063 [ 811.457425]-
> 91064 [ 811.460912] # selftests: test_lwt_seg6local [PASS]
> 91065 [ 811.460914]-
> 91066 [ 3620.461986] Thu Oct 17 14:54:05 CST 2019 detected soft_timeout
>
> ```
>
> Ignore test_lwt_seg6local and run `make run_tests -C bpf` again, task will
> hang on test_tc_tunnel.sh.
>
>
> Kushwaha also meet this issue, `make run_tests -C bpf` hang on
> test_lwt_ip_encap.sh (This test failed on my localhost).
If it keeps hanging on progressively later tests, it sounds like some
kind of stdout/stderr flushing (or reading) is missing. This is hard for
me to debug without understanding how to have the kernel tree notice my
installed libraries, though.
--
Kees Cook
prev parent reply other threads:[~2019-10-18 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 6:32 [Bug report] "make run_tests -C bpf" hanging forever Liu Yiding
2019-10-18 6:41 ` Liu Yiding
2019-10-18 6:56 ` Prabhakar Kushwaha
2019-10-18 15:01 ` Shuah Khan
2019-10-21 1:42 ` Liu Yiding
2019-10-18 16:21 ` Kees Cook [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=201910180919.B3D3618@keescook \
--to=keescook@chromium.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuyd.fnst@cn.fujitsu.com \
--cc=prabhakar.pkin@gmail.com \
--cc=skhan@linuxfoundation.org \
/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).