Bug 109988

Summary: active/backup bonding causes kernel panic
Product: [Retired] Red Hat Linux Reporter: Hrunting Johnson <hrunting>
Component: kernelAssignee: Dave Jones <davej>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 9CC: davej, pfrields, riel
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
URL: http://linux.derkeiler.com/Mailing-Lists/Kernel/2003-07/2894.html
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-01-05 03:23:13 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:
Attachments:
Description Flags
Patch to fix bonding on interfaces with no IP address none

Description Hrunting Johnson 2003-11-13 18:25:19 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET 
CLR 1.0.3705)

Description of problem:
When initiating a bonding interfacethat does not have an IP address, 
bonding panics.  The given URL highlights patches the most recent 
round of bonding updates that fixes this problem.  Attached is a 
patch that fixes the problem in the latest RH9 stable kernel released 
by RedHat.

Version-Release number of selected component (if applicable):
kernel-2.4.20-20.9

How reproducible:
Always

Steps to Reproduce:
1.setup bonding interface with no ip address
2.ifup the interface
3.
    

Actual Results:  kernel panics with reference to null pointer

Expected Results:  ifup on the bonded interface succeeds

Additional info:

Comment 1 Hrunting Johnson 2003-11-13 18:26:04 UTC
Created attachment 95950 [details]
Patch to fix bonding on interfaces with no IP address

Comment 2 Hrunting Johnson 2003-12-30 22:03:23 UTC
This was bug was listed as fixed in the latest errata.  Is that 
correct?  The bug still shows a state of NEW.

Comment 3 Dave Jones 2004-01-05 03:23:13 UTC
Patch was applied in current errata.