Re: [PATCH 01/11] vfs: copy_file_range source range over EOF should fail

Christoph Hellwig
2018-12-05T14:12:52Z

> Realistically, though, I think an attempt to read beyond EOF for the
> copy should result in behaviour like read() (i.e. return 0 bytes),
> not EINVAL. The existing behaviour needs to change, though.

I agree with this statement. So we don't we implement these semantics?