Bug 1500383

Summary:	ksc should not ignore symbols which it thinks are not exported
Product:	Red Hat Enterprise Linux 7	Reporter:	Martin Lacko <mlacko>
Component:	ksc	Assignee:	Stanislav Kozina <skozina>
Status:	CLOSED ERRATA	QA Contact:	Ziqian SUN (Zamir) <zsun>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.5	CC:	skozina, zsun
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ksc-0.9.19-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 18:36:59 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:

Description Martin Lacko 2017-10-10 13:21:53 UTC

Description of problem:
ksc does not report symbols which are not found in Module.symvers file.


Version-Release number of selected component (if applicable):
0.9.16


How reproducible:
Always


Steps to Reproduce:
1. Create kernel module, which uses 'to_nnd' symbol
2. Run ksc on this module on rhel-7.0


Actual results:
ksc prints 'WARNING: External symbol does not exist in current kernel: to_nnd', and symbol 'to_nnd' is not present in ksc-result.txt.


Expected results:
to_nnd symbol should be included in NON-WHITELIST USAGE part of ksc tool,
because this symbol is present in rhel-7.4 Module.symvers


Additional info:

Comment 2 Ziqian SUN (Zamir) 2017-10-17 06:54:08 UTC

Reproduced on RHEL-7.4

$ rpm -q ksc
ksc-0.9.18-1.el7.noarch
$ uname -r
3.10.0-693.2.2.el7.x86_64
$ ksc -k kg-use-export.ko
('WARNING: External symbol does not exist in current kernel:', 'kg_export')
Checking against architecture x86_64
Total symbol usage: 1	Total Non white list symbol usage: 0
Score: 100.00%

A copy of the report is saved in /home/nay/zsun/ksc-result.txt

Comment 8 errata-xmlrpc 2018-04-10 18:36:59 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0997