keyctl03/keyctl05/keyctl07 in ubuntu_ltp_syscalls failed with T when running with the test suite

[Po-Hsu Lin]

These 3 tests can with Trusty kernel if executed individually. But not with the syscalls test suite, nor with the keyctl pattern (sudo ./runltp -s keyctl)

If you run this test directly:
$ sudo ./runltp -s keyctl03

the test will pass without any issue:
<<<test_start>>>
tag=keyctl03 stime=1539677291
cmdline="keyctl03"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
keyctl03.c:51: PASS: Bug not reproduced

Summary:
passed 1
failed 0
skipped 0
warnings 0

But if you run the syscalls test suite:
$ sudo ./runltp -f syscalls

the test will fail with:
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=2 corefile=no
cutime=0 cstime=8
<<<test_end>>>
<<<test_start>>>
tag=keyctl03 stime=1539675107
cmdline="keyctl03"
contacts=""
analysis=exit
<<<test_output>>>
tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
keyctl03.c:43: BROK: Failed to add key

Summary:
passed 0
failed 0
skipped 0
warnings 0

This is the output for keyctl05:
<<<test_start>>>
tag=keyctl05 stime=1539678370
cmdline="keyctl05"
contacts=""
analysis=exit
<<<test_output>>>
tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
keyctl05.c:90: BROK: failed to join new session keyring: EDQUOT

Summary:
passed 0
failed 0
skipped 0
warnings 0

This is the output for keyctl07:
<<<test_start>>>
tag=keyctl07 stime=1539678370
cmdline="keyctl07"
contacts=""
analysis=exit
<<<test_output>>>
tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
keyctl07.c:57: BROK: request_key() failed with unexpected error: EDQUOT
keyctl07.c:112: BROK: Child exited with 2

Summary:
passed 0
failed 0
skipped 0
warnings 0

[Po-Hsu Lin (cypressyew)]

Bug reported upstream:
https://github.com/linux-test-project/ltp/issues/409

[Po-Hsu Lin (cypressyew)]

Tested again with 3.13.0-158-generic on a KVM node,
it looks like this issue has been addressed with this fix upstream in LTP project: https://github.com/linux-test-project/ltp/commit/75dd92ce36eac6ea6cec1f042a70a132cbd11ffc

[Po-Hsu Lin (cypressyew)]

Note, this issue can be reproduced if you run the LTP test suite with all the test together (-f runtest/syscalls)

But with the patched ubuntu_ltp_syscalls test, which will run one of each test at a time, this false alarm will gone.
http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=0aa562bd0cdc80e1427a67cb13cf8a6f76fd47d1