Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 193456

Summary:	modprobe cannot remove modules that have been renamed
Product:	Red Hat Enterprise Linux 4	Reporter:	Brian Carp <admin>
Component:	module-init-tools	Assignee:	Jon Masters <jcm>
Status:	CLOSED NOTABUG	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	jbaron
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-03-22 16:12:45 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Brian Carp 2006-05-29 05:30:31 UTC

Description of problem: If you rename a module while it is being inserted into
the kernel, a subsequent call to 'modprobe -r' will fail with a FATAL error,
although the module can be removed successfully under its new name with rmmod. 
This is also relevant in modprobe.conf with 'install' and 'remove' commands.

How reproducible: Always

Steps to Reproduce:
1. /sbin/modprobe -o some-alias some-module
2. /sbin/modprobe -r some-alias
3. /sbin/rmmod some-alias
  
Actual results: Step #2 fails with a FATAL error where step #3 succeeds.

Expected results: Step #2 should result in the same behavior as step #3.

Comment 3 Jon Masters 2006-10-12 22:28:59 UTC

I will add this to the TODO for upstream.

Comment 6 Jon Masters 2007-03-22 16:11:39 UTC

Actually, now I'm inclined to say this is *not* a bug.

modprobe -o is intended for module testing, temporarily renaming a module.
modprobe uses the modules.dep file for name tracking, so you end up having to
use rmmod directly if you rename the modules in this way - which actually will
fail in future since the key signature check will balk on the rename too.

Can you give me an example of a situation where this is causing a problem? other
than renaming on the command line?

Jon.