Thanks to Jun'ichi Nomura of NEC for addressing an annoying issue
with the "mod" command when a registered kernel module name string
does not directly relate to its module object file. For example,
the "dm_mod" module comes from the "dm-mod.ko" object file, so the
"mod -S" or "mod -s dm_mod" commands would fail to load the debug
data for that module:
crash> mod -s dm_mod
mod: cannot find or load object file for dm_mod module
crash>
Since this inconsistency seems to be always due to there being
underscores in the kernel name string and dashes in the object
filename, Jun'ichi's patch retries all module debug data load
failures after replacing the underscores with dashes, and voila,
it finds the object file:
crash> mod -s dm_mod
MODULE NAME SIZE OBJECT FILE
ffffffffa01a5380 dm_mod 66433 lib/modules/2.6.9-22.2.ELsmp/kernel/drivers/md/dm-mod.ko
crash>
And, as expected, "mod -S" now finds and loads them all.
That is the only change in 4.0-2.8.
Thanks,
Dave
