linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liu Yiding <liuyd.fnst@cn.fujitsu.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
	Prabhakar Kushwaha <prabhakar.pkin@gmail.com>,
	Kees Cook <keescook@chromium.org>
Cc: <linux-kselftest@vger.kernel.org>, Philip Li <philip.li@intel.com>
Subject: Re: [Bug report] "make run_tests -C bpf" hanging forever
Date: Mon, 21 Oct 2019 09:42:44 +0800	[thread overview]
Message-ID: <2727059f-32b7-7e7a-4d6d-6a017c6b699f@cn.fujitsu.com> (raw)
In-Reply-To: <5a1ffb6f-7c1e-42d9-5927-f46f9b41bc4f@linuxfoundation.org>

Hi, i test it on v5.3-rc4, also meet this issue.


On 10/18/19 11:01 PM, Shuah Khan wrote:
> On 10/18/19 12:56 AM, Prabhakar Kushwaha wrote:
>> On Fri, Oct 18, 2019 at 12:12 PM Liu Yiding 
>> <liuyd.fnst@cn.fujitsu.com> wrote:
>>>
>>> CC LKP mainter
>>>
>>>
>>> On 10/18/19 2:32 PM, 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.
>>>>
>>>>
>>>> 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).
>>>>
>>
>> Yes, i also faced this issue on Linux-5.3. if i kill prefix.pl or add
>> timeout in prefix.pl, test move ahead.
>>
>> somehow this issue is not present on Linux 5.4-rc3+. It could be by
>> chance and may show on any other version.
>>
>
> Kees added timeout in this commit and this went into 5.4-rc3, if recall
> correctly.
>
> commit 852c8cbf34d3b3130a05c38064dd98614f97d3a8
> Author: Kees Cook <keescook@chromium.org>
>
>     selftests/kselftest/runner.sh: Add 45 second timeout per test
>
> Do you see a timed out message from this test though. The test needs
> to fixed probably, but this timeout helps bail out.


I got TIMEOUT message for some tests, e.g. test_tunnel.sh, timeout works.

```

88418 user  :notice: [ 1258.787439] not ok 36 selftests: bpf: 
test_tunnel.sh # TIMEOUT

```


But test_lwt_seg6local still hang, it seems that this timeout is working 
for testscript and seg6local hang on tap_prefix (prefix.pl).

```

89008 user  :notice: [ 1259.886374] # [25] VAR __license type_id=24 
linkage=1
89009
89010 user  :notice: [ 1259.890166] # [26] DATASEC license size=0 vlen=1 
size == 0
89011
89012 user  :notice: [ 1259.893272] #-
89013
89014 user  :notice: [ 1259.897190] # selftests: test_lwt_seg6local [PASS]
89015
89016 user  :notice: [ 3623.763707] Fri Oct 18 16:12:56 CST 2019 
detected soft_timeout

```


>
>
> thanks,
> -- Shuah
>
>
-- 
Best regards.
Liu Yiding




  reply	other threads:[~2019-10-21  1:42 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 [this message]
2019-10-18 16:21 ` Kees Cook

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=2727059f-32b7-7e7a-4d6d-6a017c6b699f@cn.fujitsu.com \
    --to=liuyd.fnst@cn.fujitsu.com \
    --cc=keescook@chromium.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=philip.li@intel.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).