cve-2017-5754 from cve test suite in LTP failed with KVM kernel

Bug #1830682 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Fix Released
Undecided
Po-Hsu Lin
linux-kvm (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

It looks like this is cause by the absence of kallsyms:
    safe_file_ops.c:202: BROK: Failed to open FILE '/proc/kallsyms' for reading at meltdown.c:272: ENOENT

<<<test_start>>>
tag=cve-2017-5754 stime=1559026443
cmdline="meltdown"
contacts=""
analysis=exit
<<<test_output>>>
tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
meltdown.c:259: INFO: access time: cached = 49, uncached = 290, threshold = 119
safe_file_ops.c:202: BROK: Failed to open FILE '/proc/kallsyms' for reading at meltdown.c:272: ENOENT

Summary:
passed 0
failed 0
skipped 0
warnings 0
<<<execution_status>>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=2 corefile=no
cutime=21 cstime=0
<<<test_end>>>

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-1013-kvm 4.18.0-1013.13
ProcVersionSignature: User Name 4.18.0-1013.13-kvm 4.18.20
Uname: Linux 4.18.0-1013-kvm x86_64
ApportVersion: 2.20.10-0ubuntu13.3
Architecture: amd64
Date: Tue May 28 06:54:14 2019
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This test would require CONFIG_KALLSYMS to be enabled, which was not enabled on KVM kernels.

Po-Hsu Lin (cypressyew)
tags: added: linux-kvm sru-20190603 ubuntu-ltp
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Changed in ubuntu-kernel-tests:
assignee: nobody → Po-Hsu Lin (cypressyew)
status: New → In Progress
Changed in linux-kvm (Ubuntu):
status: New → Invalid
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Didn't see this anymore, mark it as fix-released.

Changed in ubuntu-kernel-tests:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.