Bug 582072 - Need a resource limit for all non-file-backed writable memory
Summary: Need a resource limit for all non-file-backed writable memory
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 12
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-04-14 02:18 UTC by Matt McCutchen
Modified: 2010-12-03 15:55 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-12-03 15:55:22 UTC
Type: ---

Attachments (Terms of Use)

Description Matt McCutchen 2010-04-14 02:18:11 UTC
Description of problem:
Several times recently, I've hit bugs where an application enters an infinite
loop allocating memory and brings the system to a halt.  I wanted to mitigate
such problems by setting a resource limit in my login scripts.  But none of the available resource limits work for this purpose:

- RLIMIT_DATA is ineffective because it covers only the data segment controlled by brk(2), and when glibc's malloc implementation gets a brk failure, it switches to anonymous mmap.  I thought the glibc behavior was perverse and filed bug 569714 about it, but that bug was marked NOTABUG without any real justification.

- RLIMIT_AS affects programs such as OpenOffice.org that map 2.5 GB of read-only shared libraries.  If I set the limit high enough so that OpenOffice.org can run, it provides no protection against a program that allocates 2.5 GB of writable memory.

- RLIMIT_RSS doesn't do anything at all in recent kernels.

Assuming the glibc behavior is not going to change, I need a resource limit that covers all non-file-backed writable memory mapped by a process.  It could be a new resource limit, or the semantics of RLIMIT_DATA could be changed if that won't break other use cases.


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

How reproducible:
See bug 569714 comment #0 to reproduce the ineffectiveness of RLIMIT_DATA.

Comment 1 Bug Zapper 2010-11-03 17:10:20 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 2 Bug Zapper 2010-12-03 15:55:22 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.