Bug 1499249

Summary:	Remove support for multiple .ko files
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:	medium	Docs Contact:
Priority:	unspecified
Version:	7.5	CC:	skozina, zsun
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
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:
Bug Depends On:	906659
Bug Blocks:

Description Martin Lacko 2017-10-06 13:00:23 UTC

Description of problem:
ksc tool should generate multiple outputs for multiple .ko files
instead of single output with all symbols from all .ko files


How reproducible:
Always


Steps to Reproduce:
1. run ksc with multiple -k options


Actual results:
Single ksc-result.txt file


Expected results:
Multiple ksc-result-<module>.txt for each input

Comment 2 Martin Lacko 2017-10-11 10:22:53 UTC

Currently, multiple --ko options are very rarely used, they don't work properly and fixing them would take a major rewrite of the whole tool, it would be better to revert changes made to solve bug #906659.

Support for multiple --ko options doesn't work properly, to make it work would require a major rewrite of the whole tool. From the recently filled bugs, we can see the feature has not been used. It would be better to revert changes made to resolve bug #906659.

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