Description of problem: /prod/[pid]/limits duplicated Version-Release number of selected component (if applicable): 5.2 beta - Kernel 2.6.18-84.el5 How reproducible: Always Steps to Reproduce: 1. Pick a pid of a running process - [pid] 2. ls -l /proc/[pid]/limits* Actual results: # ps PID TTY TIME CMD 8112 ttyS0 00:00:00 ps 23283 ttyS0 00:00:00 bash # ls -l /proc/23283/limits* -r-------- 1 root root 0 Apr 21 17:47 /proc/23283/limits -r-------- 1 root root 0 Apr 21 17:47 /proc/23283/limits # Expected results: # ls -l /proc/23283/limits* -r-------- 1 root root 0 Apr 21 17:47 /proc/23283/limits # Additional info:
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Downing the severity. I thought it might be simple to fix on your end and wanted your first implementation of this feature to have one less bug. We anticipate it may cause some scripting issues, but since this is new we don't have any legacy code that depends on it. So the current impact is low or moderate -- i.e. any scripts we wrap around this will have to account for the duplicate entries, then changed when it is corrected.
http://post-office.corp.redhat.com/archives/rhkernel-list/2008-April/msg00455.html
*** Bug 455229 has been marked as a duplicate of this bug. ***
in kernel-2.6.18-98.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5
Smoketested kernel-2.6.18-98.el5 on one of my systems. I see only one /proc/[pid]/limits file per process as expected; looks good. Thanks.
The client tested for a while and confirmed yesterday that the patch is working (with 2.6.18-105). Thank you, Cédric Internal Status set to 'Waiting on SEG' Status set to: Waiting on Tech This event sent from IssueTracker by cbuissar issue 191316
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 therefore 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-2009-0225.html