Re: NFSv4.2 server replies to Copy with length == 0
"J. Bruce Fields" <[email protected]>
| Newsgroups | gmane.ietf.nfsv4,gmane.linux.nfs |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Oct 17, 2019 at 04:43:58AM +0000, Rick Macklem wrote: > >>On Wed, Oct 16, 2019 at 07:53:45PM +0000, Kornievskaia, Olga wrote: > >>> On the client if VFS did read of len=0 then VFS itself we return 0, > >>> thus this doesn't protect against other clients sending an NFS copy > >>> with len=0. And in NFS, receiving copy with len=0 means copy to the > >>> end of the file. It's not implemented for any "intra" or "inter" code. > >Are you saying that an NFSv4.2 Copy request with a ca_count == 0 > >will not work for the Linux NFSv4.2 server? > >(I guess I'd better test this one, too.) > Tested it and it does not work, at least for Fedora30. > The server just returns 0 instead of doing a copy to EOF on the input file. > I think you should implement this, although my client does not do this now. Agreed. --b. _______________________________________________ nfsv4 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nfsv4