Red Hat Bugzilla – Bug 184544
mkinitrd improperly parses modprobe.conf
Last modified: 2007-11-30 17:07:23 EST
Description of problem:
Modules parameters in modprobe.conf that span multiple lines are not
parsed properly by mkinitrd.
The sed script in mkinitrd to extract options from modprobe.conf
incorrectly assumes a particular option fits on one line.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create entry in modprobe.conf that spans multiple lines (e.g. use a "\" to
extend the entry to the next line
2. run mkinitrd
Parameters on 2nd-N lines do not get set.
Sometimes warning messages about bad parameter name.
Bizarre panic's, not related to driver specified in modprobe.conf line, occur
when the module is loaded.
Created attachment 126351 [details]
Proposed patch for the problem
I've just seen problems with mkinitrd when I have multiple options lines for a
single module. If modprobe.conf has this:
options foo parm1
options foo parm2
then the init script in the initrd ends up with
insmod foo parm1
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
This occurs with RHEL 5 beta 1 (mkinitrd-5.1.2-1.3) as well. The same proposed
patch (with applies with an offset) fixes it.
This is a 4.5 BZ. I will clone it for 5.0.
Tom/Peter: How is this looking for 4.5?
Should be fixed in mkinitrd-184.108.40.206-1 .
Verified the original issue (described in the initial comment) is fixed in
mkinitrd-220.127.116.11-1.1. The behavior described in comment #2 (multiple option
lines instead of a continued line) does not seem to be changed.
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.