request_key03 in ubuntu_ltp_syscalls failed with T ARM64 / i386 / P8

Bug #1798052 reported by Po-Hsu Lin on 2018-10-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Undecided
Unassigned
linux (Ubuntu)
Undecided
Unassigned
Trusty
Undecided
Unassigned

Bug Description

After bug 1775370, this test is now failing with another error message,
to me it looks like there is something to do with the test case.

$ sudo ./request_key03
tst_test.c:1072: INFO: Timeout per run is 0h 05m 00s
request_key03.c:154: PASS: didn't crash while updating key of type 'encrypted'
request_key03.c:168: PASS: didn't crash while requesting key of type 'encrypted'
request_key03.c:115: BROK: unexpected error adding key of type 'trusted': ENOMEM
request_key03.c:160: BROK: add_key child exited with 2

Summary:
passed 2
failed 0
skipped 0
warnings 0
ubuntu@amaura:/opt/ltp/testcases/bin$ uname -a
Linux amaura 3.13.0-161-generic #211-Ubuntu SMP Wed Oct 3 14:52:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-161-generic 3.13.0-161.211
ProcVersionSignature: User Name 3.13.0-161.211-generic 3.13.11-ckt39
Uname: Linux 3.13.0-161-generic x86_64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Oct 16 07:01 seq
 crw-rw---- 1 root audio 116, 33 Oct 16 07:01 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Tue Oct 16 09:02:48 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Intel Corporation S1200RP
PciMultimedia:

ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-161-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro console=ttyS0,115200n8
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-161-generic N/A
 linux-backports-modules-3.13.0-161-generic N/A
 linux-firmware 1.127.24
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
dmi.board.asset.tag: ....................
dmi.board.name: S1200RP
dmi.board.vendor: Intel Corporation
dmi.board.version: G62254-407
dmi.chassis.asset.tag: ....................
dmi.chassis.type: 17
dmi.chassis.vendor: ..............................
dmi.chassis.version: ..................
dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr....................:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..............................:ct17:cvr..................:
dmi.product.name: S1200RP
dmi.product.version: ....................
dmi.sys.vendor: Intel Corporation

Po-Hsu Lin (cypressyew) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed

Tested again with 3.13.0-161 on a KVM node, it looks OK, need more check for the upcoming cycle.

Changed in ubuntu-kernel-tests:
status: New → Incomplete
Po-Hsu Lin (cypressyew) wrote :

Still failing with generic Trusty kernel

<<<test_start>>>
tag=request_key03 stime=1541576525
cmdline="request_key03"
contacts=""
analysis=exit
<<<test_output>>>
tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
request_key03.c:154: PASS: didn't crash while updating key of type 'encrypted'
request_key03.c:168: PASS: didn't crash while requesting key of type 'encrypted'
request_key03.c:115: BROK: unexpected error adding key of type 'trusted': ENOMEM
request_key03.c:160: BROK: add_key child exited with 2

Summary:
passed 2
failed 0
skipped 0
warnings 0
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=2 corefile=no
cutime=0 cstime=2
<<<test_end>>>
<<<test_start>>>
tag=cve-2017-15299 stime=1541576525
cmdline="request_key03 -b cve-2017-15299"
contacts=""
analysis=exit
<<<test_output>>>
tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
request_key03.c:154: PASS: didn't crash while updating key of type 'encrypted'
request_key03.c:168: INFO: didn't crash while requesting key of type 'encrypted'
request_key03.c:154: PASS: didn't crash while updating key of type 'trusted'
request_key03.c:168: INFO: didn't crash while requesting key of type 'trusted'
request_key03.c:154: PASS: didn't crash while updating key of type 'user'
request_key03.c:168: INFO: didn't crash while requesting key of type 'user'

Summary:
passed 3
failed 0
skipped 0
warnings 0
<<<execution_status>>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=0 corefile=no
cutime=1 cstime=24
<<<test_end>>>
<<<test_start>>>
tag=cve-2017-15951 stime=1541576526
cmdline="request_key03 -b cve-2017-15951"
contacts=""
analysis=exit
<<<test_output>>>
incrementing stop
tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
request_key03.c:154: INFO: didn't crash while updating key of type 'encrypted'
request_key03.c:168: PASS: didn't crash while requesting key of type 'encrypted'
request_key03.c:115: BROK: unexpected error adding key of type 'trusted': ENOMEM
request_key03.c:160: BROK: add_key child exited with 2

Summary:
passed 1
failed 0
skipped 0
warnings 0

Changed in ubuntu-kernel-tests:
status: Incomplete → Confirmed
Po-Hsu Lin (cypressyew) wrote :

The failure in Trusty ARM64 is a bit different:
With 3.13.0-161-generic
request_key03.c:115: BROK: unexpected error adding key of type 'trusted': ENOMEM

With 3.13.0-162-generic
request_key03.c:70: BROK: failed to join new session keyring: EDQUOT

Po-Hsu Lin (cypressyew) wrote :

With 3.13.0-163-generic ARM64 this cycle:
request_key03.c:115: BROK: unexpected error adding key of type 'trusted': ENOMEM

I think the issue in comment was caused by the test suite execution, with http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=0aa562bd0cdc80e1427a67cb13cf8a6f76fd47d1 applied, it's back to the original error message.

Po-Hsu Lin (cypressyew) wrote :

Passed with T-AMD64:
tartup='Sat Mar 16 06:36:19 2019'
tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
request_key03.c:154: PASS: didn't crash while updating key of type 'encrypted'
request_key03.c:168: PASS: didn't crash while requesting key of type 'encrypted'
request_key03.c:154: PASS: didn't crash while updating key of type 'trusted'
request_key03.c:168: PASS: didn't crash while requesting key of type 'trusted'
request_key03.c:154: PASS: didn't crash while updating key of type 'user'
request_key03.c:168: PASS: didn't crash while requesting key of type 'user'

Summary:
passed 6
failed 0
skipped 0
warnings 0

Po-Hsu Lin (cypressyew) wrote :

But still failing with ARM64 / i386

summary: - request_key03 in ubuntu_ltp_syscalls failed with T
+ request_key03 in ubuntu_ltp_syscalls failed with T ARM64 / i386
Po-Hsu Lin (cypressyew) wrote :

Found on P8 as well.

summary: - request_key03 in ubuntu_ltp_syscalls failed with T ARM64 / i386
+ request_key03 in ubuntu_ltp_syscalls failed with T ARM64 / i386 / P8
Brad Figg (brad-figg) on 2019-07-24
tags: added: cscc
Po-Hsu Lin (cypressyew) on 2019-09-16
tags: added: ubuntu-ltp-syscalls
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers