Bug 461458

Summary: kernel returns EPERM when RLIMIT_NOFILE is set to RLIM_INFINITY
Product: [Fedora] Fedora Reporter: Adam Tkac <atkac>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: bashton, ovasik, wolfgang.rupprecht
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-11-04 05:52:02 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
proposed patch none

Description Adam Tkac 2008-09-08 04:33:59 EDT
Created attachment 316052 [details]

Description of problem:
when I want set open files limit to infinity kernel returns EPERM.

Version-Release number of selected component (if applicable):
$ uname -r

How reproducible:

Steps to Reproduce:
try run attached testcase (under root, of course) and see output from strace
Actual results:
limit is not set, EPERM is returned

Expected results:
limit is set to "infinity" (currently NR_OPEN)
Comment 1 Adam Tkac 2008-09-08 04:37:12 EDT
Created attachment 316057 [details]
proposed patch
Comment 2 Dave Jones 2008-09-08 14:33:17 EDT
If you haven't already, can you send this to linux-kernel@vger.kernel.org please ?

Comment 3 Adam Tkac 2008-09-11 13:13:11 EDT
(In reply to comment #2)
> If you haven't already, can you send this to linux-kernel@vger.kernel.org
> please ?
> Thanks.

Done, already in MM tree. Would it be possible include attached patch to next distribution kernel update, please? (all F8/F9/rawhide kernels) It is needed by bind package (bug #461913). Thanks
Comment 4 Adam Tkac 2008-09-15 08:18:59 EDT
Improved version of patch is on http://lkml.org/lkml/2008/9/12/56
Comment 5 Adam Tkac 2008-09-22 09:14:53 EDT
*** Bug 461913 has been marked as a duplicate of this bug. ***
Comment 6 Brennan Ashton 2008-11-04 00:34:31 EST
Has this patch made it into the kernel, if so please close this bug.
Comment 7 Adam Tkac 2008-11-04 05:52:02 EST
Patch has been merged in 0c2d64fb6cae9aae480f6a46cfe79f8d7d48b59f (2.6.28 series), closing