NAME¶

ksc - Linux kernel module source checker

SYNOPSIS¶

ksc [ -d | --directory ] DIRECTORY

ksc [ --ko FILE | -s -p PREVIOUS_REPORT ]

OPTIONS¶

KSC accepts command-line arguments, and has both a long and short form usage. You can use either style or combine them to specify options. When the tool is run with kernel module sources it checks for all four architectures, and when run with binary kernel modules, it checks for the specific architecture for which the binary was built.

-h, --help

show this help message and exit

-c CONFIG, --config=CONFIG

path to the local ksc.conf file. If not specified the tool tries to read from ~/ksc.conf and if that is also not found then from /etc/ksc.conf.

-d DIRECTORY, --directory=DIRECTORY

path to the directory with kernel module sources.

-i, --internal

to create text files to be used internally.

-k KO, --ko=KO

path to the ko file. You should either use -d or -k to run the KSC tool, but not both. If both -d and -k option is used at the same time then only -d is used and the -k option is discarded.

-n RELEASENAME, --name=RELEASENAME

Red Hat release against which the bug is to be filed, e.g '6.5'. Default value is 6.5.

-p PREVIOUS, --previous=PREVIOUS

path to the previous resultset file and submit it as a bug to Red Hat Bugzilla.

-r RELEASE, --release=RELEASE

RHEL whitelist release used for comparison, e.g. '6.5'.

-y SYMVERS, --symvers=SYMVERS

Path to the Module.symvers file. The current kernel path is used if not specified.

-s, --submit

Submits the report to the Red Hat bugzilla (https://bugzilla.redhat.com). The credentials need to be in the /etc/ksc.conf file. The tool will prompt for bugzilla password.

The configuration file looks like below:

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

-v, --version

Prints KSC version number