Red Hat Bugzilla – Bug 137788
Extraneous data in option name for scsi_mod
Last modified: 2007-11-30 17:07:04 EST
Description of problem:
$ modinfo scsi_mod
description: "SCSI core"
parm: scsi_logging_level_Rsmp_af3dd7dc int, description "SCSI
logging level; should be zero or nonzero"
parm: scsihosts string
parm: max_scsi_luns int, description "last scsi LUN (should be
between 1 and 2^32-1)"
parm: scsi_allow_ghost_devices int, description "allow devices
marked as being offline to be accessed anyway (0 = off, else allow
ghosts on lun 0 through scsi_allow_ghost_devices - 1"
I don't think that "scsi_logging_level_Rsmp_af3dd7dc" is the real
Reproduceable with the 2.4.21-22.EL SMP kernel, the UP kernel has a
similar bizarre parameter.
The problem is that the variable in question is both export as a
module parameter and also EXPORT_SYMBOL'ed to other modules so that
they can check the variable's value at runtime (done by the SCSI_LOG
macros). Because the kernel has symbol versions enabled, a checksum
gets added to the symbol name and that shows up in the module
parameter name as well. The fix for this is simple, just
EXPORT_SYMBOL_NOVERS() the symbol instead. However, technically,
that's breaking kABI and I don't know if any external vendor modules
already rely upon the broken symbol name. I submitted a patch for
review, but the decision on whether or not to even consider including
the patch will depend upon the kABI issue.
Note: the patch was submitted post the U5 deadline and is therefore
not expected in U5, but it's now posted and if it gets approved, is
already in the queue for U6.
Reverting to ASSIGNED state until a fix is committed to CVS.
Non-kABI-breaking alternative patch posted for review by petrides
on 25-Apr-2005, now queued for next U6 build.
A fix for this problem has just been committed to the RHEL3 U6
patch pool this evening (in kernel version 2.4.21-32.3.EL).
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.