Bug 109988 - active/backup bonding causes kernel panic
Summary: active/backup bonding causes kernel panic
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 9
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL: http://linux.derkeiler.com/Mailing-Li...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-13 18:25 UTC by Hrunting Johnson
Modified: 2015-01-04 22:03 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-01-05 03:23:13 UTC
Embargoed:

Attachments (Terms of Use)
Patch to fix bonding on interfaces with no IP address (969 bytes, patch)
2003-11-13 18:26 UTC, Hrunting Johnson 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2003:394 0 normal SHIPPED_LIVE Updated 2.4 kernel fixes various bugs 2003-12-23 05:00:00 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.