Bug 138345 - problem with LARGFILE in ia32el
Summary: problem with LARGFILE in ia32el
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: ia32el
Version: 4.0
Hardware: ia64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Jakub Jelinek
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-11-08 14:12 UTC by Yoav Zach
Modified: 2007-11-30 22:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-11-11 18:05:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
testcase to demonstrate the problem of mappinga LARGFILE (941 bytes, text/plain)
2004-11-08 14:13 UTC, Yoav Zach
no flags Details
fixes the problem with mmap'ing large files (7.28 KB, patch)
2004-11-08 14:15 UTC, Yoav Zach
no flags Details | Diff

Description Yoav Zach 2004-11-08 14:12:52 UTC
Description of problem:
The file-offset field of the mmap() system call is being truncated to 
32-bits, even in programs that are compiled with all the LARGEFILE 
support.


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


How reproducible:
consistently

Steps to Reproduce:
build the attached testcase on IA-32 machine and run it on IPF 
machine with ia32el enabled.  

Actual results:
the actual output is "Start-of-file".

Expected results:
the expected output should be "Four-GBytes!!".

Additional info:

Comment 1 Yoav Zach 2004-11-08 14:13:32 UTC
Created attachment 106278 [details]
testcase to demonstrate the problem of mappinga LARGFILE

Comment 2 Yoav Zach 2004-11-08 14:15:26 UTC
Created attachment 106279 [details]
fixes the problem with mmap'ing large files

Comment 3 Yoav Zach 2004-11-08 14:17:02 UTC
same problem with ia32el that goes with EL3 U4

Comment 4 Jakub Jelinek 2004-11-08 15:36:59 UTC
Should be fixed in ia32el-1.1-9 (RHEL4) and ia32el-1.1-8.EL3 (RHEL3 U4).

Comment 5 Jay Turner 2004-11-09 12:21:14 UTC
Fix confirmed on RHEL4 with ia32el-1.1-9.


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