Description of problem: Found the following trace in our error logs during testing Fedora28: [ 2.668177] ------------[ cut here ]------------ [ 2.672800] x86/mm: Found insecure W+X mapping at address 00000000525c134b/0xffff884740000000 [ 2.681339] WARNING: CPU: 2 PID: 1 at arch/x86/mm/dump_pagetables.c:266 note_page+0x625/0x640 [ 2.689856] Modules linked in: [ 2.692916] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.16.3-301.fc28.x86_64 #1 [ 2.700221] Hardware name: Dell Computer Corporation PowerEdge 1850/0D8266, BIOS A01 09/02/2004 [ 2.708910] RIP: 0010:note_page+0x625/0x640 [ 2.713095] RSP: 0018:ffffa59c4019be40 EFLAGS: 00010286 [ 2.718321] RAX: 0000000000000000 RBX: ffffa59c4019bec8 RCX: ffffffff9b253e88 [ 2.725455] RDX: 0000000000000001 RSI: 0000000000000082 RDI: 0000000000000246 [ 2.732587] RBP: 0000000000000000 R08: 203a6d6d2f363878 R09: 000000000000022b [ 2.739711] R10: 46203a6d6d2f3638 R11: 736e6920646e756f R12: 0000000000000061 [ 2.746837] R13: 0000000000000005 R14: ffffa59c4019bec8 R15: ffff88475fa848e8 [ 2.753964] FS: 0000000000000000(0000) GS:ffff88477fd00000(0000) knlGS:0000000000000000 [ 2.762051] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 2.767796] CR2: 00007f3bf952d6a8 CR3: 000000001f20a000 CR4: 00000000000006e0 [ 2.774922] Call Trace: [ 2.777382] ? ptdump_walk_pgd_level_core+0x33a/0x480 [ 2.782432] ? rest_init+0xaa/0xaa [ 2.785835] ? ptdump_walk_pgd_level_checkwx+0x15/0x20 [ 2.790976] ? kernel_init+0x2c/0x105 [ 2.794644] ? ret_from_fork+0x35/0x40 [ 2.798394] Code: 4b 18 e9 b1 fb ff ff 4c 89 f8 25 00 01 00 00 48 89 04 24 eb c7 48 89 f2 48 c7 c7 c0 b0 09 9b c6 05 ab 41 2c 01 01 e8 95 81 03 00 <0f> 0b 48 8b 73 10 e9 64 fa ff ff 4c 8b 4b 18 e9 79 fb ff ff e9 [ 2.817273] ---[ end trace 8bd7cef00df20fd9 ]--- Version-Release number of selected component (if applicable): Fedora 28 Linux version 4.16.3-301.fc28.x86_64 (mockbuild.fedoraproject.org) (gcc version 8.0.1 20180324 (Red Hat 8.0.1-0.20) (GCC)) #1 SMP Mon Apr 23 21:59:58 UTC 2018 How reproducible: 20% Steps to Reproduce: 1. Install Fedora 28 2. Boot Fedora 28 and the trace appears in the dmesg log during boot up Actual results: above traceback during bootup Expected results: no traceback Additional info:
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs. Fedora 28 has now been rebased to 4.20.5-100.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.