Bug 1591967

Summary: Kernel 4.16.15-300.fc28.x86_64 failed the pax test This bug persists in kernel 4.17.7-200
Product: [Fedora] Fedora Reporter: Pat Kelly <pmkellly72>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: airlied, bskeggs, ewk, hdegoede, ichavero, itamar, jarodwilson, jforbes, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-23 18:33:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Log file from kernel tests. none

Description Pat Kelly 2018-06-15 21:49:47 UTC 
Created attachment 1452068 [details]
Log file from kernel tests.

Description of problem:

Kernel 4.16.15-300.fc28.x86_64 on F28 failed the PAX test. This is on a bare metal installation of F28 that is fully up to date. The hardware is a Lenovo H50-55 with an AMD A10-7800 processor, 12Gb ram, and 2 Tb hard drive.

How reproducible: Reproduces everytime the kernel tests are run.

This bug has been persistent through F27 (Bug #1546440)and now is occurring in F28 

Steps to Reproduce:
1. CD kernel-tests
2. sudo ./runtests.sh
3. The failure is recorded both on the terminal and in the log file.

Actual results:
PAX test fails

Expected results:
PAX test pass

Additional info:
The log file is attached.
Comment 1 Pat Kelly 2018-06-19 22:29:23 UTC 
This bug persists in kernel 4.16.16-300.

Starting test ./default/paxtest
Main executable randomisation (PIE) randomness is less than 28 bits (26)
Comment 2 Pat Kelly 2018-06-24 12:09:01 UTC 
This bug persists in kernel 4.17.2-200.fc28.x86_64.

Starting test ./default/paxtest
Main executable randomisation (PIE) randomness is less than 28 bits (25)
Comment 3 Pat Kelly 2018-07-01 12:17:16 UTC 
This bug persists in kernel 4.17.3-200.fc28.x86_64.

Starting test ./default/paxtest
Main executable randomisation (PIE) randomness is less than 28 bits (25)
Comment 4 Pat Kelly 2018-07-14 11:23:08 UTC 
This bug persists in kernel 4.17.5-200.fc28.x86_64.

Starting test ./default/paxtest
Main executable randomisation (PIE) randomness is less than 28 bits (25)
Comment 5 Pat Kelly 2018-07-18 01:07:26 UTC 
This bug persists in kernel 4.17.5-200.fc28.x86_64.

Starting test ./default/paxtest
Main executable randomisation (PIE) randomness is less than 28 bits (25)
Comment 6 Pat Kelly 2018-07-18 01:10:14 UTC 
This bug persists in kernel 4.17.6-200.fc28.x86_64.

Starting test ./default/paxtest
Main executable randomisation (PIE) randomness is less than 28 bits (25)
Comment 7 Pat Kelly 2018-07-22 13:16:38 UTC 
This bug persists in kernel 4.17.7-200.fc28.x86_64.

Starting test ./default/paxtest
Main executable randomisation (PIE) randomness is less than 28 bits (26)
Comment 8 Justin M. Forbes 2018-07-23 18:32:10 UTC 
*** Bug 1546440 has been marked as a duplicate of this bug. ***
Comment 9 Justin M. Forbes 2018-07-23 18:32:47 UTC 
This is actually an issue with the test, and how AMD is working after the spectre/meltdown updates. It needs to be fixed in the test.  The issue should be tracked on https://pagure.io/kernel-tests/issues