2. EL 8
  3. ksc
  4. ksc(1)

Scroll to navigation

ksc(1) User Commands ksc(1)

NAME

ksc - report symbols used by kernel modules

SYNOPSIS

ksc -k FILE ... [OPTIONS]

ksc -k FILE ... -s [OPTIONS]

ksc -s -p KSC_RESULT [OPTIONS]

DESCRIPTION

ksc produces and submits reports of symbols used by kernel object FILEs (specified by -k). Resulting report is always saved to ~/ksc-result.txt.

For more on report generation, see -k.

For more on report submission, see -s.

ENVIRONMENT

It is highly recommended that ksc is used on the latest minor version of RHEL, and to make sure, prior to ksc usage, to update kabi-stablelists as well as kernel-devel-provided Module.symvers. This can be accomplished, for example, by issuing:

yum update kernel-abi-stablelists kernel-devel

It is also possible to use the -y (--symvers) option to explicitly state the location of Module.symvers file to make sure that accurate and up-to-date kABI data be provided to ksc.

OPTIONS

You may freely mix different option styles.

Show help message and exit.
Read config options from CONFIG file. If not supplied, ksc will use ~/ksc.conf. If not found, /etc/ksc.conf will be used instead.
Read symbol justifications from KSC_RESULT file and use them in the new report. It is important to note that placeholder justifications and reference justifications are ignored by this option and re-generated every time.

This option may be specified multiple times. KSC_RESULT file order is determined by the order of arguments passed to ksc. If there are two conflicting non-placeholder/non-reference justifications for a kernel module A.ko symbol S in multiple report files at the same time, it will be carried over from the last one specified on the command line.

Symbol justifications can be carried over within the same kernel module only. Justifications do not propagate through references (i.e., if you justify usage of S for A.ko, B.ko references justification in A.ko, and you run ksc without A.ko, justification is not carried over and you will be asked to specify).

Collect used symbols in kernel object FILE.
Multiple -k arguments may be supplied, in which case different FILEs are placed in distinct sections of the ~/ksc-result.txt file.

All kernel object FILEs must be build against the same architecture.

If multiple FILEs are supplied, ksc report won't include symbols exported by any one of the FILEs. This allows for bulk collection of symbols of a functionally dependent set of kernel modules without having to filter symbols coming from other modules.

Omit any symbols exported by FILE from the report. Use this option if other modules (which are part of the report) depend on symbols exported by FILE, but FILE itself is not to be reported at this time.
RHEL RELEASE against which the bug is to be filed, e.g '6.5'.
Specified PREVIOUS file is marked for submission to Red Hat Bugzilla.
To submit, you need to use -s.
RHEL RELEASE used for symbol comparison with stablelists, e.g. '6.5'.
Path to Module.symvers SYMVERS file used to check symbol presence in the the kernel. If not specified, current kernel version is used to determine the path and Module.symvers of the currently running kernel is used.

You are notified whenever symbol is not present in the Module.symvers file.

Submit the report to the Red Hat Bugzilla (https://bugzilla.redhat.com). Credentials used in submission need to be set a config file (see FILES section below). If API key is not set, ksc will prompt for Bugzilla password.

This option needs to be supplemented with -k or -p.

If used with -k, report gets generated, opened in an editor for you to make changes, saved in ~/ksc-result.txt, and submitted. You may interrupt submission by pressing ^C.

Prints ksc version.

FILES

~/ksc-result.txt
Report produced by ksc.

~/ksc.conf (/etc/ksc.conf)
Local (global) ksc config file. Global config file is used only when local config file does not exist. Syntax is as follows:

[bugzilla]
user=user@redhat.com
partner=partner-name
partnergroup=partner-group
server=https://bugzilla.redhat.com/xmlrpc.cgi
api_key=api_key

These are default values. Whenever a field has such a value (except the server field), it will always be treated as though it were undefined/left blank.

EXAMPLES

Process a.ko file using system-provided stablelist and Module.symvers files. Reports symbols used by a.ko that are not in stablelist, requesting justification for their use.

Process a.ko file using system-provided stablelist and user-provided Module.symvers (/tmp/Module.symvers) files. Reports symbols used by a.ko that are not in stablelist, requesting justification for their use.

Process a.ko and b.ko files using system-provided stablelist and Module.symvers files. Reports symbols used by both a.ko and b.ko that are not in stablelist, requesting justification for their use. Only one justification per symbol is required. Any mention of an already justified symbol come with an automatically generated references.

Process a.ko and b.ko files using system-provided stablelist and Module.symvers files. Reports symbols used by both a.ko and b.ko that are not in stablelist and not exported by either c.ko or d.ko, requesting justification for their use. Only one justification per symbol is required. Any mention of an already justified symbol come with an automatically generated references.

Process a.ko and b.ko files using system-provided stablelist and Module.symvers files. Reports symbols used by both a.ko and b.ko that are not in stablelist, requesting justification for their use. Only one justification per symbol is required. Any mention of an already justified symbol come with an automatically generated references. Justifications already present in previous-report.txt are carried over to the newly generated one.

Submit a report to bugzilla.

November 2018 ksc - Version 1.9