Bug 155633 - Function hugetlbfs_statfs of RHEL3 kernel returns incorrect block size on RHEL3U5Beta
Function hugetlbfs_statfs of RHEL3 kernel returns incorrect block size on RHE...
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Larry Woodman
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-04-21 22:07 EDT by Zhang Yanmin
Modified: 2007-11-30 17:07 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-07-13 15:16:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
A patch to fix it (530 bytes, text/plain)
2005-04-21 22:07 EDT, Zhang Yanmin
no flags Details

  None (edit)
Description Zhang Yanmin 2005-04-21 22:07:49 EDT
Description of problem:
Function hugetlbfs_statfs of RHEL3 kernel set PAGE_CACHE_SZIE as the block 
size. It's incorrect. The right one is HPAGE_SIZE.

Version-Release number of selected component (if applicable):
RHEL3-U5-Beta Kernel, 2.4.21-31.EL

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Zhang Yanmin 2005-04-21 22:07:50 EDT
Created attachment 113506 [details]
A patch to fix it
Comment 2 Larry Woodman 2005-05-03 10:04:27 EDT
OK, patch looks and works correct.  Will queue this change up for RHEL3-U6 since
U5 is already frozen.

Larry Woodman
Comment 3 Ernie Petrides 2005-05-11 17:42:58 EDT
Hello, Zhang.  Could you please explain what problem occurs when
the block size for hugetlbfs is reported as PAGE_CACHE_SIZE?
Comment 4 Zhang Yanmin 2005-05-11 21:00:17 EDT
Currently, I can't find problems except it might mislead applications.
Comment 5 Larry Woodman 2005-07-13 15:16:57 EDT
Patch was rejected by Ret Hat engineering.

Larry Woodman

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