Displaying 3 results from an estimated 3 matches for "newdirfd".
Did you mean:
newdir
2019 Jan 18
0
[klibc:master] rename, renameat: Use renameat2() system call
.../
diff --git a/usr/klibc/renameat.c b/usr/klibc/renameat.c
new file mode 100644
index 0000000..10c8882
--- /dev/null
+++ b/usr/klibc/renameat.c
@@ -0,0 +1,12 @@
+#include <fcntl.h>
+#include <stdio.h>
+
+#ifndef __NR_renameat
+
+int renameat(int olddirfd, const char *oldpath,
+ int newdirfd, const char *newpath)
+{
+ return renameat2(olddirfd, oldpath, newdirfd, newpath, 0);
+}
+
+#endif /* __NR_renameat */
2018 Jul 17
1
[PATCH klibc 1/2] rename, renameat: Use renameat2() system call
...newpath);
+ return renameat2(AT_FDCWD, oldpath, AT_FDCWD, newpath, 0);
}
#endif /* __NR_rename */
--- /dev/null
+++ b/usr/klibc/renameat.c
@@ -0,0 +1,12 @@
+#include <fcntl.h>
+#include <stdio.h>
+
+#ifndef __NR_renameat
+
+int renameat(int olddirfd, const char *oldpath,
+ int newdirfd, const char *newpath)
+{
+ return renameat2(olddirfd, oldpath, newdirfd, newpath, 0);
+}
+
+#endif /* __NR_renameat */
--- a/usr/klibc/SYSCALLS.def
+++ b/usr/klibc/SYSCALLS.def
@@ -116,6 +116,7 @@ int chdir(const char *);
int fchdir(int);
<?> int rename(const char *, const char *);
<?&g...
2009 May 03
6
[RFC] The reflink(2) system call.
Hi everyone,
I described the reflink operation at the Linux Storage &
Filesystems Workshop last month. Originally implemented as an
ocfs2-specific ioctl, the consensus was that it should be a syscall from
the get-go. Here's some first-cut patches.
For people who have not seen reflink, either at LSF or on the
ocfs2 wiki, the first patch contains
Documentation/filesystems/reflink.txt to