Bug 133460

Summary: setrlimit/getrlimit should be per-process, not per-thread
Product: [Fedora] Fedora Reporter: Roland McGrath <roland>
Component: kernelAssignee: Roland McGrath <roland>
Status: CLOSED NEXTRELEASE QA Contact: Brian Brock <bbrock>
Severity: low Docs Contact:
Priority: medium    
Version: rawhideCC: wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-01-03 08:31:46 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: 142791    
Attachments:
Description Flags
test program for multithreaded behavior of setrlimit
none
patch vs 2.6.9-rc2-bk9 to fix the behavior none

Description Roland McGrath 2004-09-24 07:07:12 UTC 
Description of problem:

POSIX specifies that 

Version-Release number of selected component (if applicable):
2.6.9-rc2

How reproducible:
100%

Steps to Reproduce:
1. Compile attached program with -lpthread.
2. Run it.  See it writes 3 bytes.
3. Realize it should have died with SIGXFSZ.
  
Actual results:
no SIGXFSZ

Expected results:
killed by SIGXFSZ

Additional info:
Fix on the way.
Comment 1 Roland McGrath 2004-09-24 07:08:45 UTC 
Created attachment 104249 [details]
test program for multithreaded behavior of setrlimit

gcc -g -o mt-rlimit mt-rlimit.c -lpthread

Run with some args, demonstrates the single-threaded case and dies with
SIGXFSZ.
Run with no args, demonstrates the multi-threaded case and only dies with
SIGXFSZ if the kernel is fixed.
Comment 2 Roland McGrath 2004-09-24 08:01:17 UTC 
Created attachment 104251 [details]
patch vs 2.6.9-rc2-bk9 to fix the behavior

I've submitted this patch upstream, waiting for feedback.
Comment 3 Roland McGrath 2004-10-20 06:13:55 UTC 
This patch has gone in upstream, after 2.6.9; hopefully in 2.6.10 release.
Comment 4 Roland McGrath 2005-01-03 08:31:46 UTC 
2.6.10 has this fixed.  Only the RLIMIT_CPU behavior is not quite correct,
everything else should be right now.