pkey01 from ubuntu_ltp_syscalls failed on B-aws-fips / X-4.15 AWS

Bug #1849093 reported by Po-Hsu Lin on 2019-10-21
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Undecided
Unassigned

Bug Description

This issue was only spotted on AWS instance "i3en.24xlarge" with B-aws-fips kernel (aws-fips : 4.15.0-2002.2), test interrupted with:
    tst_test.c:1163: BROK: Test killed by SIGBUS!

Test log:
 tag=pkey01 stime=1570753169 dur=0 exit=exited stat=2 core=no cu=0 cs=0
 startup='Fri Oct 11 00:19:29 2019'
 tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s
 pkey01.c:164: INFO: Set PKEY_DISABLE_ACCESS on (MAP_ANONYMOUS|MAP_PRIVATE) buffer
 pkey01.c:187: PASS: Child ended by SIGSEGV as expected
 pkey01.c:191: INFO: Remove PKEY_DISABLE_ACCESS from the buffer
 pkey01.c:197: PASS: Read buffer success, buffer[0] = 0
 pkey01.c:164: INFO: Set PKEY_DISABLE_ACCESS on (MAP_ANONYMOUS|MAP_SHARED) buffer
 pkey01.c:187: PASS: Child ended by SIGSEGV as expected
 pkey01.c:191: INFO: Remove PKEY_DISABLE_ACCESS from the buffer
 pkey01.c:197: PASS: Read buffer success, buffer[0] = 0
 pkey01.c:164: INFO: Set PKEY_DISABLE_ACCESS on (MAP_ANONYMOUS|MAP_PRIVATE|MAP_HUGETLB) buffer
 pkey01.c:187: PASS: Child ended by SIGSEGV as expected
 pkey01.c:191: INFO: Remove PKEY_DISABLE_ACCESS from the buffer
 tst_test.c:1163: BROK: Test killed by SIGBUS!

 Summary:
 passed 5
 failed 0
 skipped 0
 warnings 0

Probably a hiccup. As this test has passed on other instances like i3en.2xlarge, c5n.xlarge, c5.large, t3.medium, r5.large

Po-Hsu Lin (cypressyew) on 2019-10-21
description: updated
Po-Hsu Lin (cypressyew) on 2019-10-21
tags: added: 4.15 aws bionic sru-20190930 ubuntu-ltp-syscalls
Po-Hsu Lin (cypressyew) wrote :

Can be found on X-4.15 AWS (4.15.0-1056.58~16.04.1-aws) on some instances
* c5.metal
* i3en.24xlarge
* r5.metal

summary: - pkey01 from ubuntu_ltp_syscalls failed on B-aws-fips
+ pkey01 from ubuntu_ltp_syscalls failed on B-aws-fips / X-4.15 AWS
tags: added: xenial
tags: added: sru-20191111
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers