Bug 410311 - New kernel syscall sys_rlimit64 for resource limits
Summary: New kernel syscall sys_rlimit64 for resource limits
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.6
Hardware: All
OS: Linux
high
low
Target Milestone: ---
: ---
Assignee: Jerome Marchand
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-12-04 13:08 UTC by Adam Stokes
Modified: 2010-06-24 14:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-24 14:08:17 UTC


Attachments (Terms of Use)

Description Adam Stokes 2007-12-04 13:08:10 UTC
Description of problem:
In this particular case users of ppc64 are unable to set things like memlock
higher than 4G

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

How reproducible:
Everytime

Steps to Reproduce:
Set memlock higher than 4G in /etc/security/limits.conf

This simple application shows its effect :
#include <sys/resource.h>
#include <stdio.h>
#include <stdlib.h>

int main ()
{
  struct rlimit rlim;
  
  rlim.rlim_max = 5961560;
  rlim.rlim_cur = rlim.rlim_max;

  if ( setrlimit(8, &rlim) < 0) {
    fprintf(stderr,"Failed to set memlock max\n");
    exit(1);
  }
  fprintf(stderr,"rlim_cur: %ld\n",rlim.rlim_cur);
  return 1;
}
  
Actual results:
Fails to set memlock higher than 4G.

Expected results:
Allow for higher threshold

Additional info:

Comment 1 Linda Wang 2008-06-06 10:18:57 UTC
if you are using 4.6.9, then it is RHEL4 not RHEL5.
In RHEL4, have you try the PPC64 largesmp version of the kernel?

Comment 2 Vitaly Mayatskikh 2008-06-09 13:47:55 UTC
Hardlimit for memlock is set in compile time and equals to 8 pages (32kb). And
it is not possible to increase hardlimit value in run time. Adam, can you
provide us with more information?

Comment 4 Jerome Marchand 2010-06-24 12:31:56 UTC
I can not reproduce the issue, neither on RHEL4.6 nor on more recent 4.8. 
If you still experience problem, please provide us with more info:
 - what exact kernel version do you use,
 - what error do you get.


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