Messages in this thread |  | | Date | Thu, 26 Oct 2000 00:06:17 +0200 | From | Andrea Arcangeli <> | Subject | Re: nfsv3d wrong truncates over 4G |
| |
On Wed, Oct 25, 2000 at 10:49:52PM +0200, Trond Myklebust wrote: > This should already be done IIRC. At least nfsd_open() always sets > O_LARGEFILE.
Yes, that is just working right.
> we should be returning EOVERFLOW rather than EBIG.
Right.
2.4.0-test10-pre4 is also buggy because it doesn't check for O_LARGEFILE while reading and writing (it should return EOVERFLOW from read and EBIG during writes).
2.2.18pre17aa1 allows anybody to open a file larger than 2G (that seems not to be completly in sync with the specs) but it has all the necessary runtime checks during read/write. Just search for O_LARGEFILE in the lfs patch. That needs to be forward ported to 2.4.x.
Andrea - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |