On 2020/1/2 12:50, Eryu Guan wrote:
On Thu, Jan 02, 2020 at 11:53:12AM +0800, Xiao Yang wrote:
> lo_copy_file_range() passes -errno to fuse_reply_err() and then
fuse_reply_err()
> changes it to errno again, so that subsequent fuse_send_reply_iov_nofree()
catches
> the wrong errno.(i.e.
On Thu, Jan 02, 2020 at 11:53:12AM +0800, Xiao Yang wrote:
> lo_copy_file_range() passes -errno to fuse_reply_err() and then
> fuse_reply_err()
> changes it to errno again, so that subsequent fuse_send_reply_iov_nofree()
> catches
> the wrong errno.(i.e. reports "fuse: bad error value: ...").
>
lo_copy_file_range() passes -errno to fuse_reply_err() and then fuse_reply_err()
changes it to errno again, so that subsequent fuse_send_reply_iov_nofree()
catches
the wrong errno.(i.e. reports "fuse: bad error value: ...").
Make fuse_send_reply_iov_nofree() accept the correct -errno by passing