> In practice, many 2.1 file systems go through generic_file_read, which
> silently truncates the file offset to 32 bits. Even if this was fixed,
> it would be truncated shortly after that, because the readpage
> interface does not support loff_t.
>
> As for mapping large files: no way. First, mmap(2) does not support
> passing large offsets. If it would, the page cache would truncate the
> MS 32 bits. If the page cache would be large-file-aware, the file
> systems would truncate.
>
> Finally, we have stat(2): It does not support large files, either.
> This is partially due to struct inode storing only 32 bits for the
> file size. Same for file locking.
Is this true for all platforms or do the Alpha and Ultrasparc do better?
Jim