Bug 166524

Summary: Erratic behaviour when system fd limit reached
Product: Red Hat Enterprise Linux 4 Reporter: Peter Staubach <staubach>
Component: kernelAssignee: Peter Staubach <staubach>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: jbaron
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHSA-2006-0132 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-03-07 19:36:35 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: 168429    
Attachments:
Description Flags
Proposed patch
none
Proposed patch
none
Proposed patch none

Description Peter Staubach 2005-08-22 20:28:35 UTC
+++ This bug was initially created as a clone of Bug #166364 +++

Escalated to Bugzilla from IssueTracker

Comment 1 Peter Staubach 2005-08-26 14:18:46 UTC
Created attachment 118156 [details]
Proposed patch

Comment 2 Peter Staubach 2005-08-26 14:36:51 UTC
The problem is the ordering of creating the entry in the directory and
allocating the file struct to reference the file.  The file struct was
getting allocated second, but should be allocated before the directory
entry is created.  Thus, if the allocation fails, then the error can be
returned without creating the directory entry.

Comment 3 Peter Staubach 2005-09-20 12:53:52 UTC
Created attachment 119024 [details]
Proposed patch

Comment 4 Peter Staubach 2005-11-18 19:42:37 UTC
Created attachment 121242 [details]
Proposed patch

The previous proposed patch was incomplete.

Comment 8 Red Hat Bugzilla 2006-03-07 19:36:35 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 the 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-2006-0132.html