Bug 40561

Summary:	Kernal module cipcb is not unloaded after ifdown
Product:	[Retired] Red Hat Linux	Reporter:	Martin C. Messer <mmesser>
Component:	cipe	Assignee:	Nalin Dahyabhai <nalin>
Status:	CLOSED CURRENTRELEASE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1
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:	2003-07-22 16:51:31 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 Martin C. Messer 2001-05-14 16:21:04 UTC

Description of Problem:

'ifdown cipcb0' does not remove the cipcb module from memory, which causes
problems if one executes 'ifup cipcb0' before the module cleaner (rmmod
-as) is run.

How Reproducible:

Only if you ifdown and ifup before the module cleaner runs.

Steps to Reproduce:
1.  ifup cipcb0 
2.  ifdown cipcb0
3.  lsmod
4.  ifup cipcb0  

Actual Results:

Step 3 shows cipcb loaded but not used and ready for autoclean.
Step 4, if ran before autocleaning, either errors with 'resource busy', or
doesn't error but cipe then acts eradically.

Expected Results:

Can cipe clean it's own module?

Additional Information:

Comment 1 Scott Schmit 2001-07-11 21:52:37 UTC

This isn't a bug. The bug is that cipcb has to be rmmod'd at all. It worked in
wolverine, but broke since then. After all, we don't do this with ethX, etc...