Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 125915 - brctl seg faults after upgrade to kernel 2.6.6-1.427
brctl seg faults after upgrade to kernel 2.6.6-1.427
Product: Fedora
Classification: Fedora
Component: bridge-utils (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: David Woodhouse
Depends On:
  Show dependency treegraph
Reported: 2004-06-13 20:15 EDT by saul
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-09 04:51:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description saul 2004-06-13 20:15:34 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
rv:1.7) Gecko/20040608

Description of problem:
After installing kernel 2.6.6-1.427, all attempts to
use bridging, via brctl, fail with the utility
immediately coring.

A search through kernel changelogs show a number
of changes in the 2.6.6-2.6.7 timeframe to the
kernel about bridging, and bridge-util changelogs
show changes that track the kernel changes.

An upgrade to the current bridge-util (1.0.4)
fixed the problem for me.

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

How reproducible:

Steps to Reproduce:
1.Run brctl

Actual Results:  Segmentation fault.

Expected Results:  Bridging.

Additional info:

This renders bridging completely non-functional under
this kernel.
Comment 1 Matthew Miller 2005-04-26 11:36:26 EDT
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.

Note You need to log in before you can comment on or make changes to this bug.