From: Florian Weimer <fweimer@redhat.com>
Date: Tue, 3 Mar 2020 11:11:01 +0000 (+0100)
Subject: Linux: copy_file_range syscall number is always available
X-Git-Tag: glibc-2.32~563
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a72ae22d5d9951a97b4e3c3101cc651ef1a01da3;p=thirdparty%2Fglibc.git

Linux: copy_file_range syscall number is always available

Due to the built-in tables, __NR_copy_file_range is always defined.

Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
---

diff --git a/sysdeps/unix/sysv/linux/copy_file_range.c b/sysdeps/unix/sysv/linux/copy_file_range.c
index 65597ca0259..a73c89f079a 100644
--- a/sysdeps/unix/sysv/linux/copy_file_range.c
+++ b/sysdeps/unix/sysv/linux/copy_file_range.c
@@ -25,11 +25,6 @@ copy_file_range (int infd, __off64_t *pinoff,
                  int outfd, __off64_t *poutoff,
                  size_t length, unsigned int flags)
 {
-#ifdef __NR_copy_file_range
   return SYSCALL_CANCEL (copy_file_range, infd, pinoff, outfd, poutoff,
                          length, flags);
-#else
-  __set_errno (ENOSYS);
-  return -1;
-#endif
 }