usb.rc does not correctly parse blacklist files in Ubuntu Breezy

Bug #27891 reported by Cory Snider
6
Affects Status Importance Assigned to Milestone
hotplug (Ubuntu)
Fix Released
Medium
Scott James Remnant (Canonical)

Bug Description

The maybe_modprobe function of /etc/hotplug/usb.rc does not match blacklisted
modules the same way as modprobe interprets modules.
usb.rc treats - and _ differently, while modprobe treats them as if they were
the same.

Steps to Reproduce:
1) Add a module to the blacklist with a - or _ in the name, switching a - for a
_ or vice versa depending on the way it was entered in usb.rc. i.e. putting
ehci_hcd into the blacklist file instead of ehci-hcd (which is how it is
represented in usb.rc)
2) Restart hotplug

Actual Results:
The module loads

Expected Results:
The module is not loaded

Fully-patched Ubuntu Breezy i386.
Bug may exist on other platforms and in other files with the maybe_modprobe
method copy+pasted.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

This is a breezy bug, and the infrastructure has changed completely in dapper --
we now use modprobe's native alias expansion and blacklist support to load modules.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.