On Wed, 27 Jan 1999 20:20:27 +0200 (EET), Itai Nahshon
<nahshon@actcom.co.il> said:
>> No, the "offset maximum" is a fancy way of saying "the maximum possible
>> offset_t supported for this file descriptor".
> I got to this conclusion after reading more manuals.
> In that case open(2) should have already failed with EOVERFLOW:
> [EOVERFLOW]
> The named file is a regular file and the size of the file canno
> be represented correctly in an object of type off_t.
No, because there are extensions to the API in the LFS (Large File
Summit) standard which let you open a larger file by using open64(). If
you do that, the "offset maximum" for that file descriptor may be larger
than 2^31-1, even if the file was initially smaller than that when you
opened it.
--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/