hw-detect modprobes blindly, ignoring blacklists
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hw-detect (Ubuntu) |
Fix Released
|
Low
|
Mathieu Trudel-Lapierre | ||
Xenial |
Fix Released
|
Low
|
Mathieu Trudel-Lapierre |
Bug Description
[Impact]
Any system requiring specific modules to be blacklisted at install-time, when using server or alternate images.
[Test cases]
Boot the installer w/ this boot/kernel cmdline option (the alias w/ dashes is not required, but is here just in case):
modprobe.
On the dialog for username/password, select Go Back, then Exit to shell:
The blacklist is detected/present in the config:
~ # modprobe -c | grep alua
blacklist scsi_dh_alua
blacklist scsi-dh-alua
But the module is insmod-ed anyway:
~ # modprobe -v -n scsi-dh-alua
insmod /lib/modules/
Unless -b is used:
~ # modprobe -v -n -b scsi-dh-alua
~ #
[Regression Potential]
Failure to load kernel modules at boot time due to unexpectedly blacklisted modules would consistute a regression for this bug report.
== Comment: #0 - Mauricio Faria De Oliveira - 2016-07-11 18:47:59 ==
---Problem Description---
modprobe does not honor blacklist options in kernel cmdline unless -b is used (at least on the installer)
The modprobe.blacklist option is required as a work-around until a solution to a device-driver bug is found (IBM LTC bug 138273).
I've gone through the code of the kmod src pkg, but didn't spot anything obvious.
Passing along to the Ubuntu team.
Contact Information = Mauricio Faria de Oliveira <email address hidden> / Lekshmi C. Pillai <email address hidden>
---Steps to Reproduce---
Boot the installer w/ this boot/kernel cmdline option (the alias w/ dashes is not required, but is here just in case):
modprobe.
On the dialog for username/password, select Go Back, then Exit to shell:
The blacklist is detected/present in the config:
~ # modprobe -c | grep alua
blacklist scsi_dh_alua
blacklist scsi-dh-alua
But the module is insmod-ed anyway:
~ # modprobe -v -n scsi-dh-alua
insmod /lib/modules/
Unless -b is used:
~ # modprobe -v -n -b scsi-dh-alua
~ #
Installer kernel:
[ 0.000000] Linux version 4.4.0-21-generic (buildd@
tags: | added: architecture-ppc64le bugnameltc-143679 severity-high targetmilestone-inin16041 |
Changed in ubuntu: | |
assignee: | nobody → Taco Screen team (taco-screen-team) |
affects: | ubuntu → linux (Ubuntu) |
affects: | hw-detect (Ubuntu) → linux (Ubuntu) |
affects: | linux (Ubuntu) → hw-detect (Ubuntu) |
affects: | hw-detect (Ubuntu) → linux (Ubuntu) |
affects: | hw-detect (Ubuntu) → linux (Ubuntu) |
affects: | linux (Ubuntu) → hw-detect (Ubuntu) |
tags: |
added: targetmilestone-inin16042 removed: targetmilestone-inin16041 |
Changed in hw-detect (Ubuntu): | |
assignee: | Taco Screen team (taco-screen-team) → Mathieu Trudel-Lapierre (cyphermox) |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in hw-detect (Ubuntu): | |
status: | Triaged → In Progress |
Changed in hw-detect (Ubuntu Xenial): | |
status: | New → In Progress |
importance: | Undecided → Low |
assignee: | nobody → Mathieu Trudel-Lapierre (cyphermox) |
description: | updated |
According to the man page modprobe is functioning as designed.