search for: resolve_no_symlinks

...), but there is an anomaly: I can access the shares using |smbclient| from the macOS host, or from any VM (running Windows, running Linux), but they appear empty except for (sub-)directories. With logging on, I spotted entries like: |openat_pathref_fsp_nosymlink: SMB_VFS_OPENAT(., dummy-1.pdf, RESOLVE_NO_SYMLINKS) returned 78 Function not implemented => NT_STATUS_NOT_SUPPORTED readlink_talloc: SMB_VFS_READLINKAT() failed: No such file or directory read_symlink_reparse: readlink_talloc failed: NT_STATUS_OBJECT_NAME_NOT_FOUND openat_pathref_fsp_nosymlink: create_open_symlink_err failed: NT_STATUS_OBJEC...

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

...000), real(1000, 0)] source3/smbd/files.c:77(fsp_new) fsp_new: allocated files structure (9 used) [2024/06/06 19:02:40.521372, 10, pid=1173240, effective(1000, 1000), real(1000, 0)] source3/smbd/files.c:978(openat_pathref_fsp_nosymlink) openat_pathref_fsp_nosymlink: SMB_VFS_OPENAT(., dfstest, RESOLVE_NO_SYMLINKS) returned 40 Too many levels of symbolic links => NT_STATUS_OBJECT_PATH_NOT_FOUND [2024/06/06 19:02:40.521437, 10, pid=1173240, effective(1000, 1000), real(1000, 0)] source3/smbd/mangle_hash2.c:415(is_mangled) is_mangled dfstest ? [2024/06/06 19:02:40.521466, 10, pid=1173240, effective(1000,...

....17 the situation improved a lot again: - Pathnames given by a client are devided into dirname and basename. ? The amount of syscalls to validate dirnames is reduced to 2 syscalls ? (openat, close) per component. On modern Linux kernels (>= 5.6) smbd ? makes use of the openat2() syscall with RESOLVE_NO_SYMLINKS, ? in order to just use 2 syscalls (openat2, close) for the whole dirname. - Contended path based operations used to generate a lot of unsolicited ? wakeup events causing thundering herd problems, which lead to masive ? latencies for some clients. These events are now avoided in order ? to pro...

....17 the situation improved a lot again: - Pathnames given by a client are devided into dirname and basename. ? The amount of syscalls to validate dirnames is reduced to 2 syscalls ? (openat, close) per component. On modern Linux kernels (>= 5.6) smbd ? makes use of the openat2() syscall with RESOLVE_NO_SYMLINKS, ? in order to just use 2 syscalls (openat2, close) for the whole dirname. - Contended path based operations used to generate a lot of unsolicited ? wakeup events causing thundering herd problems, which lead to masive ? latencies for some clients. These events are now avoided in order ? to pro...

....17 the situation improved a lot again: - Pathnames given by a client are devided into dirname and basename. ? The amount of syscalls to validate dirnames is reduced to 2 syscalls ? (openat, close) per component. On modern Linux kernels (>= 5.6) smbd ? makes use of the openat2() syscall with RESOLVE_NO_SYMLINKS, ? in order to just use 2 syscalls (openat2, close) for the whole dirname. - Contended path based operations used to generate a lot of unsolicited ? wakeup events causing thundering herd problems, which lead to masive ? latencies for some clients. These events are now avoided in order ? to pro...

....17 the situation improved a lot again: - Pathnames given by a client are devided into dirname and basename. ? The amount of syscalls to validate dirnames is reduced to 2 syscalls ? (openat, close) per component. On modern Linux kernels (>= 5.6) smbd ? makes use of the openat2() syscall with RESOLVE_NO_SYMLINKS, ? in order to just use 2 syscalls (openat2, close) for the whole dirname. - Contended path based operations used to generate a lot of unsolicited ? wakeup events causing thundering herd problems, which lead to masive ? latencies for some clients. These events are now avoided in order ? to pro...

....17 the situation improved a lot again: - Pathnames given by a client are devided into dirname and basename. ? The amount of syscalls to validate dirnames is reduced to 2 syscalls ? (openat, close) per component. On modern Linux kernels (>= 5.6) smbd ? makes use of the openat2() syscall with RESOLVE_NO_SYMLINKS, ? in order to just use 2 syscalls (openat2, close) for the whole dirname. - Contended path based operations used to generate a lot of unsolicited ? wakeup events causing thundering herd problems, which lead to masive ? latencies for some clients. These events are now avoided in order ? to pro...

....17 the situation improved a lot again: - Pathnames given by a client are devided into dirname and basename. ? The amount of syscalls to validate dirnames is reduced to 2 syscalls ? (openat, close) per component. On modern Linux kernels (>= 5.6) smbd ? makes use of the openat2() syscall with RESOLVE_NO_SYMLINKS, ? in order to just use 2 syscalls (openat2, close) for the whole dirname. - Contended path based operations used to generate a lot of unsolicited ? wakeup events causing thundering herd problems, which lead to masive ? latencies for some clients. These events are now avoided in order ? to pro...

....17 the situation improved a lot again: - Pathnames given by a client are devided into dirname and basename. ? The amount of syscalls to validate dirnames is reduced to 2 syscalls ? (openat, close) per component. On modern Linux kernels (>= 5.6) smbd ? makes use of the openat2() syscall with RESOLVE_NO_SYMLINKS, ? in order to just use 2 syscalls (openat2, close) for the whole dirname. - Contended path based operations used to generate a lot of unsolicited ? wakeup events causing thundering herd problems, which lead to masive ? latencies for some clients. These events are now avoided in order ? to pro...

....17 the situation improved a lot again: - Pathnames given by a client are devided into dirname and basename. ? The amount of syscalls to validate dirnames is reduced to 2 syscalls ? (openat, close) per component. On modern Linux kernels (>= 5.6) smbd ? makes use of the openat2() syscall with RESOLVE_NO_SYMLINKS, ? in order to just use 2 syscalls (openat2, close) for the whole dirname. - Contended path based operations used to generate a lot of unsolicited ? wakeup events causing thundering herd problems, which lead to masive ? latencies for some clients. These events are now avoided in order ? to pro...

....17 the situation improved a lot again: - Pathnames given by a client are devided into dirname and basename. ? The amount of syscalls to validate dirnames is reduced to 2 syscalls ? (openat, close) per component. On modern Linux kernels (>= 5.6) smbd ? makes use of the openat2() syscall with RESOLVE_NO_SYMLINKS, ? in order to just use 2 syscalls (openat2, close) for the whole dirname. - Contended path based operations used to generate a lot of unsolicited ? wakeup events causing thundering herd problems, which lead to masive ? latencies for some clients. These events are now avoided in order ? to pro...

....17 the situation improved a lot again: - Pathnames given by a client are devided into dirname and basename. ? The amount of syscalls to validate dirnames is reduced to 2 syscalls ? (openat, close) per component. On modern Linux kernels (>= 5.6) smbd ? makes use of the openat2() syscall with RESOLVE_NO_SYMLINKS, ? in order to just use 2 syscalls (openat2, close) for the whole dirname. - Contended path based operations used to generate a lot of unsolicited ? wakeup events causing thundering herd problems, which lead to masive ? latencies for some clients. These events are now avoided in order ? to pro...

After joining a Samba server to domain using either Winbind or using ADBridge (PBIS), enumeration time of listing files from windows file explorer for that share is roughly (9) seconds for a folder containing 30k files consisting of both large (upto 15GB in size) and small size files (as low as KB's). Intitially, without setting logging to "0" and disabling smb max server protocol in