Bug 506875 - kernel: ptrace: don't use REMOVE_LINKS/SET_LINKS for reparenting [rhel-4.9]
Summary: kernel: ptrace: don't use REMOVE_LINKS/SET_LINKS for reparenting [rhel-4.9]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.9
Hardware: All
OS: Linux
urgent
medium
Target Milestone: rc
: ---
Assignee: Oleg Nesterov
QA Contact: Petr Beňas
URL:
Whiteboard:
Depends On:
Blocks: 519446
TreeView+ depends on / blocked
 
Reported: 2009-06-19 03:40 UTC by Eugene Teo (Security Response)
Modified: 2015-01-04 22:58 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-16 15:45:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:0263 0 normal SHIPPED_LIVE Important: Red Hat Enterprise Linux 4.9 kernel security and bug fix update 2011-02-16 15:14:55 UTC

Description Eugene Teo (Security Response) 2009-06-19 03:40:57 UTC 
Description of problem:
There are places where kernel uses REMOVE_LINKS/SET_LINKS while changing process's ->parent.  Use add_parent/remove_parent instead, they don't abuse of global process list.

Upstream commit:
http://git.kernel.org/linus/9b678ece42893b53aae5ed7cb8d7cb261cacb72c
Comment 4 Vivek Goyal 2009-07-07 18:11:59 UTC 
Committed in 89.5.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/
Comment 9 Petr Beňas 2010-11-15 13:00:46 UTC 
Reproduced in 2.6.9-89.4.E and verified in 2.6.9-89.5.EL.
Comment 11 errata-xmlrpc 2011-02-16 15:45:38 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-2011-0263.html
Note You need to log in before you can comment on or make changes to this bug.