Re: nfsv3d wrong truncates over 4G

From: Matti Aarnio (matti.aarnio@zmailer.org)
Date: Wed Oct 25 2000 - 15:25:14 EST


On Wed, Oct 25, 2000 at 09:34:49PM +0200, Trond Myklebust wrote:
> >>>>> " " == Matti Aarnio <matti.aarnio@zmailer.org> writes:
> > When the NFS server does file open, does it do it with
> > O_LARGEFILE, or not ? Is there a standardized way to pass
> > that flag over NFSv3 ?
>
> All NFSv3 operations are 64-bit and LFS-compliant. There's therefore
> no need for an O_LARGEFILE flag.

        Ok, so there is no such flag over the NFSv3 XDR protocol,
        however:

        The NFSv3 SERVER (for which Andrea made his patch)
        actually MUST open local files with O_LARGEFILE
        flag set. (Otherwise e.g. EXT2 may reject the open.)

        The NFSv3 CLIENT code must do post-open verification,
        that if the opened file has size exceeding 2G-1, and
        O_LARGEFILE flag is not set, the opened file must be
        closed, and caller must be informed of the rejection
        with -EFBIG status.
        (If possible, do that size verification before open.)

        Am I making any sense ?

> Cheers,
> Trond

/Matti Aarnio
-
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/



This archive was generated by hypermail 2b29 : Tue Oct 31 2000 - 21:00:17 EST