From 5a659ccc0ec217ab02a4c273a1f6d346a359560a Mon Sep 17 00:00:00 2001 From: Florian Weimer Date: Fri, 28 Jun 2019 09:39:21 +0200 Subject: io: Remove copy_file_range emulation [BZ #24744] The kernel is evolving this interface (e.g., removal of the restriction on cross-device copies), and keeping up with that is difficult. Applications which need the function should run kernels which support the system call instead of relying on the imperfect glibc emulation. Reviewed-by: Adhemerval Zanella --- manual/llio.texi | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'manual') diff --git a/manual/llio.texi b/manual/llio.texi index e89affd666..447126b7eb 100644 --- a/manual/llio.texi +++ b/manual/llio.texi @@ -1404,10 +1404,13 @@ failure occurs. The return value is zero if the end of the input file is encountered immediately. If no bytes can be copied, to report an error, @code{copy_file_range} -returns the value @math{-1} and sets @code{errno}. The following -@code{errno} error conditions are specific to this function: +returns the value @math{-1} and sets @code{errno}. The table below +lists some of the error conditions for this function. @table @code +@item ENOSYS +The kernel does not implement the required functionality. + @item EISDIR At least one of the descriptors @var{inputfd} or @var{outputfd} refers to a directory. @@ -1437,9 +1440,6 @@ reading. The argument @var{outputfd} is not a valid file descriptor open for writing, or @var{outputfd} has been opened with @code{O_APPEND}. - -@item EXDEV -The input and output files reside on different file systems. @end table In addition, @code{copy_file_range} can fail with the error codes -- cgit v1.2.3-70-g09d2