Bug 457006

Summary:	ipv6: use timer pending to fix bridge reference count problem [rhel-5.3]
Product:	Red Hat Enterprise Linux 5	Reporter:	Eugene Teo (Security Response) <eteo>
Component:	kernel	Assignee:	Jiri Pirko <jpirko>
Status:	CLOSED ERRATA	QA Contact:	Martin Jenner <mjenner>
Severity:	low	Docs Contact:
Priority:	low
Version:	5.3	CC:	davem, dzickus, lwang, mgahagan, nhorman, rkhan, tao, tgraf, wwlinuxengineering
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-01-20 20:24:18 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:
Bug Depends On:
Bug Blocks:	457009, 457010, 457012

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 1 Eugene Teo (Security Response) 2008-07-29 07:53:43 UTC

Proposed upstream patch:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=847499ce71bdcc8fc542062df6ebed3e596608dd

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. ***