vma05 in mm from ubuntu_ltp failed on 5.3 / 5.4 kernel

[Po-Hsu Lin]

Test failed with:
   tag=vma05 stime=1568998082 dur=0 exit=exited stat=1 core=no cu=23 cs=4

Need to check if it has something to do with AppArmor

 startup='Fri Sep 20 16:48:02 2019'
 vma05 1 TINFO: timeout per run is 0h 5m 0s
 vma05 1 TFAIL: [vsyscall] reporting wrong
 vma05 1 TPASS: [vdso] backtrace complete
 vma05 2 TINFO: AppArmor enabled, this may affect test results
 vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root)
 vma05 2 TINFO: loaded AppArmor profiles: none

 Summary:
 passed 1
 failed 1
 skipped 0
 warnings 0

 tag=vma05 stime=1568998082 dur=0 exit=exited stat=1 core=no cu=23 cs=4
 startup='Fri Sep 20 16:48:02 2019'
 vma05 1 TINFO: timeout per run is 0h 5m 0s
 vma05 1 TFAIL: [vsyscall] reporting wrong
 vma05 1 TPASS: [vdso] backtrace complete
 vma05 2 TINFO: AppArmor enabled, this may affect test results
 vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root)
 vma05 2 TINFO: loaded AppArmor profiles: none

 Summary:
 passed 1
 failed 1
 skipped 0
 warnings 0

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1845863

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Po-Hsu Lin (cypressyew)]

Found on B-AWS-5.3

[Po-Hsu Lin (cypressyew)]

Found on E-AWS 5.3 (5.3.0-1009.10) across all AMD64 instances (not on ARM64 instances)

[Po-Hsu Lin (cypressyew)]

This issue could be found on 5.3 Eoan and 5.3 Eoan Oracle as well.
Looks like it's affecting all the 5.3 kernels.

[Po-Hsu Lin (cypressyew)]

BTW the failure on Eoan generic kernel (5.3.0-25.27) can only be found on AMD64

[Po-Hsu Lin (cypressyew)]

In 5.3 kernel, the pattern in /proc/self/maps will be like:
ffffffffff600000-ffffffffff601000 --xp 00000000 00:00 0 [vsyscall]

So it does not match the test case expectation:
ffffffffff600000-ffffffffff601000[[:space:]]r-xp

To be more precise, the r-xp became --xp

And to comment #5, this is expected as this test was designed for x86_64 ($(uname -m) = "x86_64" )

[Po-Hsu Lin (cypressyew)]

This can be found on Focal 5.4 as well.

[Po-Hsu Lin (cypressyew)]

Fix applied upstream:
https://github.com/linux-test-project/ltp/commit/1c0e86d28f34e2d7b0d8772700595aafec18ca76#diff-3db6fdadc5686c4bea264b3bdeb6afe3

Didn't see this failure in 5.4.0-23.27 and 5.3.0-47.39

I am closing this bug.