Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 155943 - /proc/$$/auxv has zero size
/proc/$$/auxv has zero size
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ingo Molnar
Brian Brock
Depends On:
Blocks: 116894
  Show dependency treegraph
Reported: 2005-04-25 18:24 EDT by Andrew Cagney
Modified: 2012-06-20 12:00 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 12:00:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrew Cagney 2005-04-25 18:24:08 EDT
Description of problem:

/proc's per-process AUXV has a finite size (the size doesn't change during the
lifetime of the process) yet

$ ls -l /proc/$$/auxv
-r--------  1 cagney cagney 0 Apr 25 18:14 /proc/12877/auxv
$ file /proc/$$/auxv
/proc/12877/auxv: empty
$ wc -c !$
wc -c /proc/$$/auxv
0 /proc/12877/auxv
$ cat /proc/$$/auxv | wc -c

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


How reproducible:


Expected results:

$ ls -l /proc/$$/auxv
-r--------   1 cagney   cagney       152 Apr 25 15:09 /proc/23038/auxv
$ wc -c /proc/$$/auxv
     152 /proc/23038/auxv
Comment 1 Ingo Molnar 2005-09-15 18:37:35 EDT
/proc files are special and rarely match their true size. Check out 'ls -l
/proc'. Does this issue have any practical relevance?
Comment 3 Jiri Pallich 2012-06-20 12:00:56 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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