Bug 457006 - ipv6: use timer pending to fix bridge reference count problem [rhel-5.3]
Summary: ipv6: use timer pending to fix bridge reference count problem [rhel-5.3]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.3
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Jiri Pirko
QA Contact: Martin Jenner
URL:
Whiteboard:
: 449947 489895 (view as bug list)
Depends On:
Blocks: 457009 457010 457012
TreeView+ depends on / blocked
 
Reported: 2008-07-29 07:51 UTC by Eugene Teo (Security Response)
Modified: 2018-10-20 02:37 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-01-20 20:24:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2009:0225 0 normal SHIPPED_LIVE Important: Red Hat Enterprise Linux 5.3 kernel security and bug fix update 2009-01-20 16:06:24 UTC

Description Eugene Teo (Security Response) 2008-07-29 07:51:52 UTC
Using expires field instead of timer_pending() may cause bridge reference count
problem in the ipv6 FIB timer management.

Comment 2 Don Zickus 2008-09-03 03:40:55 UTC
in kernel-2.6.18-107.el5
You can download this test kernel from http://people.redhat.com/dzickus/el5

Comment 5 Andy Gospodarek 2008-10-22 13:31:06 UTC
*** Bug 449947 has been marked as a duplicate of this bug. ***

Comment 8 errata-xmlrpc 2009-01-20 20:24:18 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2009-0225.html

Comment 10 Thomas Graf 2009-12-01 12:56:39 UTC
*** Bug 489895 has been marked as a duplicate of this bug. ***


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