disabled modules remain in tmpfs between service restarts

Bug #258541 reported by TJ
2
Affects Status Importance Assigned to Milestone
linux-restricted-modules (Ubuntu)
Fix Released
Low
Ben Collins

Bug Description

Affects Hardy (not checked Intrepid).

/etc/init.d/linux-restricted-modules-common does nothing when stopped. As a result, if the user disables modules using DISABLED_MODULES in /etc/default/linux-restricted-modules-common and restarts LRM the previously built modules are still in the mounted tmpfs.

This prevents user-built drivers from being used.

lrm-manager should check for the existence of a disabled driver and remove it:

        if [ "$1" = "$module" ]; then
          CURRENT_MODULE_DISABLED="true"
          if [ -e /lib/modules/"$KVER"/volatile/$module.ko ]; then
            rm -f /lib/modules/"$KVER"/volatile/$module.ko
          fi
          if [ "$LIST" = "yes" ]; then
            echo "$module"
          fi
          break
        else

TJ (tj)
description: updated
Changed in linux-restricted-modules:
assignee: nobody → ben-collins
importance: Undecided → Low
milestone: none → intrepid-alpha-5
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-restricted-modules - 2.6.27-1.1

---------------
linux-restricted-modules (2.6.27-1.1) intrepid; urgency=low

  [Ben Collins]

  * lrm-manager: Remove disabled modules from tmpfs
    - LP: #258541
  * lrm-manager/postinst/postrm: Fixes to have volatile created correctly
  * broadcom/madwifi: Updates for iwe_stream_add_*() function calls
  * Bump release to 2.6.27-1

 -- Ben Collins <email address hidden> Tue, 26 Aug 2008 10:32:24 -0400

Changed in linux-restricted-modules:
status: Fix Committed → Fix Released
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.