search for: at_symlink_nofollow

07.06.2024 07:59, Michael Tokarev wrote: > 07.06.2024 07:54, Jeremy Allison wrote: >>> msdfs is broken in 4.19.? It worked fine in 4.18. > > This is not entirely true. Nope. Things are more interesting than that. I've a 4.19 installation where msdfs links works both in listing and when specified directly. There are 2 other installations of 4.19 where msdfs links

...ooks like this is caused by the getxattr call which is only present with vfs_fruit activated and introduces an additional delay of ~ 0.00033 s per listed file. strace -T reveals the following with vfs_fruit activated: newfstatat(35, "03915", {st_mode=S_IFREG|0660, st_size=1265, ...}, AT_SYMLINK_NOFOLLOW) = 0 <0.000243> fcntl(20, F_SETLKW, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=8368, l_len=1}) = 0 <0.000010> fcntl(20, F_SETLKW, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=8368, l_len=1}) = 0 <0.000009> stat("stroth/testfiles_10000-50000/10000/03915", {st_mode=S_IFR...

...ibisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.8, 1:9.10.3.dfsg.P4-8ubuntu1.10), libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.8, 1:9.10.3.dfsg.P4-8ubuntu1.10) End-Date: 2018-01-18? 04:34:32 strace rsync : 30743 23:34:47 newfstatat(3, "6737", {st_mode=S_IFDIR|0755, st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0 30743 23:34:47 newfstatat(3, "6741", {st_mode=S_IFDIR|0755, st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0 30743 23:34:47 getdents(3, /* 0 entries */, 131072) = 0 30743 23:34:47 munmap(0x7fa4feae7000, 135168) = 0 30743 23:34:47 close(3)???????????????? = 0 30743 23:34:47 write(2, &quo...

...gt; 1:9.10.3.dfsg.P4-8ubuntu1.10), > libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.8, > 1:9.10.3.dfsg.P4-8ubuntu1.10) > End-Date: 2018-01-18 04:34:32 > > > > strace rsync : > > 30743 23:34:47 newfstatat(3, "6737", {st_mode=S_IFDIR|0755, st_size=4096, > ...}, AT_SYMLINK_NOFOLLOW) = 0 > 30743 23:34:47 newfstatat(3, "6741", {st_mode=S_IFDIR|0755, st_size=4096, > ...}, AT_SYMLINK_NOFOLLOW) = 0 > 30743 23:34:47 getdents(3, /* 0 entries */, 131072) = 0 > 30743 23:34:47 munmap(0x7fa4feae7000, 135168) = 0 > 30743 23:34:47 close(3) = 0 >...

...xattr call which is only present with vfs_fruit > activated and introduces an additional delay of ~ 0.00033 s > per listed file. > > strace -T reveals the following with vfs_fruit activated: > > newfstatat(35, "03915", {st_mode=S_IFREG|0660, st_size=1265, ...}, > AT_SYMLINK_NOFOLLOW) = 0 <0.000243> > fcntl(20, F_SETLKW, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=8368, > l_len=1}) = 0 <0.000010> > fcntl(20, F_SETLKW, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=8368, > l_len=1}) = 0 <0.000009> > stat("stroth/testfiles_10000-50000/10000/03...

(resending, sorry for duplicates) On 01/24/2018 05:59 PM, Dietmar Putz wrote: > strace rsync : > > 30743 23:34:47 newfstatat(3, "6737", {st_mode=S_IFDIR|0755, > st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0 > 30743 23:34:47 newfstatat(3, "6741", {st_mode=S_IFDIR|0755, > st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0 > 30743 23:34:47 getdents(3, /* 0 entries */, 131072) = 0 > 30743 23:34:47 munmap(0x7fa4feae7000, 135168) = 0 > 30743 23:34:47 close(3)???????????????? = 0 &gt...

...untu1.10), > libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.8, > 1:9.10.3.dfsg.P4-8ubuntu1.10) > End-Date: 2018-01-18? 04:34:32 > > > > strace rsync : > > 30743 23:34:47 newfstatat(3, "6737", {st_mode=S_IFDIR|0755, > st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0 > 30743 23:34:47 newfstatat(3, "6741", {st_mode=S_IFDIR|0755, > st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0 > 30743 23:34:47 getdents(3, /* 0 entries */, 131072) = 0 > 30743 23:34:47 munmap(0x7fa4feae7000, 135168) = 0 > 30743 23:34:47 close(3)?????...

...-0,0 +1,26 @@ +#include <errno.h> +#include <fcntl.h> +#include <unistd.h> + +extern int __faccessat(int dirfd, const char *pathname, int mode); + +int faccessat(int dirfd, const char *pathname, int mode, int flags) +{ + + /* ignoring AT_EACCESS subsequently */ + if (flags & ~(AT_SYMLINK_NOFOLLOW | AT_EACCESS)) { + errno = EINVAL; + return -1; + } + if (dirfd < 0 && dirfd != AT_FDCWD) { + errno = EBADF; + return -1; + } + if (!pathname) { + errno = ENOENT; + return -1; + } + + /* FIXME: use AT_SYMLINK_NOFOLLOW value */ + return __faccessat(dirfd, pathname, mode); +} -- 1.7...

Fwiw, rsync error 3 is: "Errors selecting input/output files, dirs" On January 19, 2018 7:36:18 AM PST, Dietmar Putz <dietmar.putz at 3qsdn.com> wrote: >Dear All, > >we are running a dist. repl. volume on 4 nodes including >geo-replication >to another location. >the geo-replication was running fine for months. >since 18th jan. the geo-replication is faulty.

...64 (1:9.10.3.dfsg.P4-8ubuntu1.8, >> 1:9.10.3.dfsg.P4-8ubuntu1.10) >> End-Date: 2018-01-18? 04:34:32 >> >> >> >> strace rsync : >> >> 30743 23:34:47 newfstatat(3, "6737", {st_mode=S_IFDIR|0755, >> st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0 >> 30743 23:34:47 newfstatat(3, "6741", {st_mode=S_IFDIR|0755, >> st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0 >> 30743 23:34:47 getdents(3, /* 0 entries */, 131072) = 0 >> 30743 23:34:47 munmap(0x7fa4feae7000, 135168) = 0 >> 30743 23...

...IVATE|MAP_ANONYMOUS, -1, 0) = 0x7efdccf7f000 getdents(3, /* 6 entries */, 131072) ? ?= 168 getdents(3, /* 0 entries */, 131072) ? ?= 0 lseek(3, 0, SEEK_SET) ? ? ? ? ? ? ? ? ? = 0 getdents(3, /* 6 entries */, 131072) ? ?= 168 newfstatat(3, "test", {st_mode=S_IFDIR|0755, st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0 newfstatat(3, ".trashcan", {st_mode=S_IFDIR|0755, st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0 getdents(3, /* 0 entries */, 131072) ? ?= 0 munmap(0x7efdccf7f000, 135168) ? ? ? ? ?= 0 close(3) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 0 write(2, "rsync: getcwd(): No such file or"...,...

Hi, As a quick workaround for geo-replication to work. Please configure the following option. gluster vol geo-replication <mastervol> <slavehost>::<slavevol> config access_mount true The above option will not do the lazy umount and as a result, all the master and slave volume mounts maintained by geo-replication can be accessed by others. It's also visible in df output.

On 02/05/2018 01:33 PM, Florian Weimer wrote: > Do you have strace output going further back, at least to the proceeding > getcwd call?? It would be interesting to see which path the kernel > reports, and if it starts with "(unreachable)". I got the strace output now, but it very difficult to read (chdir in a multi-threaded process ?). My current inclination is to blame

...(chdir(path) == -1) { - perror(path); - exit(1); - } - dir = opendir(path); if (dir == NULL) { perror(path); exit(1); } + dir_fd = dirfd(dir); while ((dent = readdir(dir)) != NULL) { - if (lstat(dent->d_name, &st)) { + if (fstatat(dir_fd, dent->d_name, &st, + AT_SYMLINK_NOFOLLOW)) { perror(dent->d_name); exit(1); } (preformat) ? do_preformat(&st) : - do_stat(&st, dent->d_name); + do_stat(&st, dir_fd, dent->d_name); } closedir(dir); @@ -218,7 +216,7 @@ int main(int argc, char *argv[]) S_ISDIR(st.st_mode) ? do_dir(arg...

...path, const char *name, const void *value, size_t size) +{ + int attrfd; + size_t bufpos,w; + + STRUCT_STAT fst; + + mode_t mode = S_IRUSR | S_IWUSR | S_IRGRP | S_IWGRP; + + do_lstat(path,&fst); + + if(S_ISLNK(fst.st_mode)) { + errno=EPERM; + return(-1); + } + + attrfd = attropen(path, name, AT_SYMLINK_NOFOLLOW|O_CREAT|O_RDWR,mode); + + if(attrfd>0) { + + for(bufpos=0;bufpos<size;) { + w = write(attrfd, value+bufpos, size); + if(w<0) return -errno; + bufpos+=w; + + } + close(attrfd); + return (bufpos); +} +return 0; +} + +int sys_lremovexattr(const char *path, const char *name) +{ + int attr...

On Thu, 2016-10-13 at 20:08 -0400, Kevin Korb wrote: > I don't remember whether or not you said you were running rsync over > ssh but if you are you can also debug the ssh layer.  You can even do > it at both ends.... > > On the server run a debugging sshd on an alternate port with: > /usr/sbin/sshd -dDp222 > (note that this will only accept 1 connection, debug to the

...644 index 0000000..9a9e1e1 --- /dev/null +++ b/usr/klibc/lchown.c @@ -0,0 +1,12 @@ +#include <fcntl.h> +#include <unistd.h> +#include <sys/syscall.h> + +#ifndef __NR_lchown + +int lchown(const char *path, uid_t owner, gid_t group) +{ + return fchownat(AT_FDCWD, path, owner, group, AT_SYMLINK_NOFOLLOW); +} + +#endif /* __NR_lchown */ diff --git a/usr/klibc/link.c b/usr/klibc/link.c new file mode 100644 index 0000000..1d4b70e --- /dev/null +++ b/usr/klibc/link.c @@ -0,0 +1,12 @@ +#include <fcntl.h> +#include <unistd.h> +#include <sys/syscall.h> + +#ifndef __NR_link + +int link(c...

Dear All, we are running a dist. repl. volume on 4 nodes including geo-replication to another location. the geo-replication was running fine for months. since 18th jan. the geo-replication is faulty. the geo-rep log on the master shows following error in a loop while the logs on the slave just show 'I'nformations... somehow suspicious are the frequent 'shutting down connection'

...7251 lgetxattr("osd/0.6ed_head/DIR_D/DIR_E/DIR_6", "user.cephos.phash.contents", 0x0, 0) = -1 ENODATA (No data available) 8: 27253 <... lsetxattr resumed> ) = 0 9: 27253 utimensat(AT_FDCWD, "osd/0.6ed_head/DIR_D/DIR_E/DIR_6", {UTIME_NOW, {1407992261, 0}}, AT_SYMLINK_NOFOLLOW) = 0 a: 27251 write(2, "rsync: get_xattr_data: lgetxattr"..., 181) = 181 lines 0-2, 3-6 and 5-8, show concurrent access of both rsync processes to the same directory. This wouldn't be a problem, not even for replaying batches, for the lsetxattr would put the intended xattr value in...

...ecking whether fdopendir is declared... (cached) yes checking whether fdopendir works... yes checking for fchmodat... yes checking for fstatat... yes checking for mkdirat... yes checking for openat... yes checking for unlinkat... yes checking for fchownat... yes checking whether fchownat works with AT_SYMLINK_NOFOLLOW... yes checking for struct statfs.f_type... yes checking whether getcwd handles long file names properly... no, but it is partly working checking for getpagesize... yes checking whether getcwd aborts when 4k < cwd_length < 16k... no checking whether the compiler generally respects inline... y...