[compiler-rt] [compiler-rt][rtsan] copy_file_range interception for Linux. (PR #129026)

[via llvm-commits]

================
@@ -312,6 +312,18 @@ INTERCEPTOR(int, ftruncate64, int fd, off64_t length) {
 #define RTSAN_MAYBE_INTERCEPT_FTRUNCATE64
 #endif
 
+#if SANITIZER_LINUX
+INTERCEPTOR(ssize_t, copy_file_range, int fdin, off_t *off_int, int fdout,
+            off_t *off_out, size_t len, unsigned int flags) {
+  __rtsan_notify_intercepted_call("copy_file_range");
+  return REAL(copy_file_range)(fdin, off_int, fdout, off_out, len, flags);
+}
+#define RTSAN_MAYBE_INTERCEPT_COPY_FILE_RANGE                                  \
----------------
davidtrevelyan wrote:

Is that not OK? `INTERCEPT_FUNCTION` is a no-op (empty macro definition) on mac. Although I do appreciate that it's more expressive to not write it if we're not intercepting it. What do you think @cjappl ?

https://github.com/llvm/llvm-project/pull/129026