Bug 519386

Summary: [RHEL4.5] Even if a process have received data but schedule() in select() cannot return [rhel-4.8.z]
Product: Red Hat Enterprise Linux 4 Reporter: RHEL Program Management <pm-rhel>
Component: kernelAssignee: Vitaly Mayatskikh <vmayatsk>
Status: CLOSED ERRATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.5CC: dfeng, dhoward, fleitner, jolsa, kzhang, pm-eus, snagar, takafumi.miki.gc, tao
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Due to insufficient memory barriers in the network code, a process sleeping in select() may have missed notifications about new data. In rare cases, this bug may have caused a process to sleep forever.
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-10-22 15:09:39 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: 494404    
Bug Blocks:    

Description RHEL Program Management 2009-08-26 12:58:36 UTC
This bug has been copied from bug #494404 and has been proposed
to be backported to 4.8 z-stream (EUS).

Comment 3 Danny Feng 2009-09-29 02:33:24 UTC
committed in 89.0.12

Comment 7 errata-xmlrpc 2009-10-22 15:09:39 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-1522.html

Comment 9 Douglas Silas 2011-01-30 23:27:10 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Due to insufficient memory barriers in the network code, a process sleeping in select() may have missed notifications about new data. In rare cases, this bug may have caused a process to sleep forever.