similar to: O_PATH, FreeBSD & acl_xx_fd

On Tue, May 30, 2023 at 09:57:37AM +0200, Peter Eriksson via samba wrote: >I?ve been looking at an issue when compiling Samba on FreeBSD 13 with the vfs_zfsacl module. > >It seems the logic that detect O_PATH support in Samba doesn?t work right with FreeBSD 13 (since it has implemented O_PATH support) and especially with the acl_get_fd() function. This is a bug (or rather a missing

Urgh? I modified the FreeBSD kernel to allow all_xx_fd() calls on O_PATH descriptors and that seems make vfs_zfsacl to work fine. Not 100% tested but I could atleast view and modify the ACL on some stuff from a Windows client via Samba that way. I?m not sure I?ll be able to get them to implement this ?officially? though. Reading ACLs via an O_PATH-opened descriptor seems to be on the way of

On 11/08/2013 09:12 AM, Steve Capper wrote: > diff --git a/usr/klibc/lstat.c b/usr/klibc/lstat.c > new file mode 100644 > index 0000000..0282eec > --- /dev/null > +++ b/usr/klibc/lstat.c > @@ -0,0 +1,17 @@ > +#include <fcntl.h> > +#include <unistd.h> > +#include <sys/types.h> > +#include <sys/stat.h> > +#include <sys/syscall.h> > +

Solaris OS has ZFS as primary filesystem, that has own implementation of ACL (NFS v4 ACL). Samba uses zfsacl and acl_xattr modules for converting NT ACL to ZFS ACL and extended attributes of file in this OS. ZfsOnLinux team ported ZFS as a number of kernel-linked modules to Linux OS, so ZFS on Linux supports NFS ACL, deduplication, compresson and other features of Solaris ZFS v.28. But NFS ACL is

Hi, I want to use Samba with ZFS volume, although I know 3.0.25c dose not work with ZFS volume. And I found modules/vfs_zfsacl.c on Samba-3.0.26. ( http://viewcvs.samba.org/cgi-bin/viewcvs.cgi/branches/SAMBA_3_0_26/source/modules/ ) But I can't find samba-3.0.26.tar.gz on samba.org. So, I have two question. 1. It is possible to download samba-3.0.26.tar.gz (or something another which can use

On Sat, July 11, 2020 04:32, Andrea Venturoli wrote: > On 2020-07-10 14:47, James B. Byrne wrote: >> FreeBSD-12.1p6 IOCage thick jails on ZFS, samba-4.10.15: > > Can you post the smb.conf of both DCs? > > Just out of curiosity, are you also using vfs_zfsacl? Yes. smb.confs DC1 and DC2: /zroot/iocage/jails/smb4-1a/root/usr/local/etc/smb4.conf [root at vhost04 ~ (master)]#

Hi, I'm working on bug 122, consolidating the interface to the SymbolTable class. In doing so, I found the function below which traverses the symbol table but apparently unnecessarily. Before I remove the traversal, I thought I better check with you guys. Posted this to the list because it looks like _everyone_ has edited this file :) In the code below, the IOB variable is the only thing in

Hi Rowland, I see this in the ZFS props, if that’s related, you might be referring to something in ext3 that im not aware of at the moment. pool/myshare aclinherit restricted default pool/myshare acltype off default So, if you heard that I was going to use

I mis-stated what I think should be deleted. The block of code from "GlobalVariable *IOB = 0;" to the end of the loop should be delted because the only effect the loop has is on the IOB variable and that variable is never used after the loop. Reid. On Tue, 2004-05-11 at 18:14, Reid Spencer wrote: > Hi, > > I'm working on bug 122, consolidating the interface to the

On Wed, Sep 16, 2020 at 5:41 AM Andrew Walker <walker.aj325 at gmail.com> wrote: > > > On Tue, Sep 15, 2020 at 11:43 PM Budi Janto via samba < > samba at lists.samba.org> wrote: > >> >> >> On 9/16/20 2:27 AM, Andrew Walker wrote: >> > >> > >> > On Tue, Sep 15, 2020 at 2:58 PM Budi Janto via samba >> > <samba at

And, one more weird thing in this function. The FILESize static variable is never initialized so its likely initial value is 0 due to zero fill on many MMUs. The value is never written and used as a divisor. Why hasn't this function caused an arithmetic violation? Because the IOBBase point, also a static variable is initialized to zero and never modified and used in a conditional that thwarts

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

I'd like to use the zfsacl module now in 3.2.0 (http://websvn.samba.org/cgi-bin/viewcvs.cgi/branches/SAMBA_3_2_0/source/modules/vfs_zfsacl.c?rev=23856&view=log) with 3.0.25a prebuilt on OpenSolaris. Is this possible? If so, will it require building Samba from source or is there a way to use it with the pre-existing binary? -- Pete

Hi people, I'm testing Samba 4.0.17 running as classic pdc mode under FreeBSD 10 and 9.2 , all shares are on ZFS volumes, i would like to use UFS instead of ZFS , but according the wiki page https://wiki.freebsd.org/NFSv4_ACLs nfsv4 inheritance flags works only with ZFS , i tried the parameters inherit acls and inherit permissions with module vfs_zfsacl on the UFS shares but got no success

OS platform: FreeBSD 10.1-RELEASE-p25 Filesystem: ZFS Samba version: upgraded from 4.1.17 to 4.1.22 Problem: I have been using the shadow_copy2 and zfsacl VFS modules to enable access control and the Previous Versions feature for Windows clients. With /usr/local/etc/smb4.conf configured this way (excerpt): vfs objects = shadow_copy2 zfsacl shadow:snapdir = .zfs/snapshot

Hi In QEMU 8 virtiofsd has been removed in favor of the rust version. Which includes options that are not longer supported, Do you have a view on what should be used going forwards to support virtiofsd in libvirt with qemu 8? The options are showing as depreciated, -o <compat-options>... Options in a format compatible with the legacy implementation [deprecated] Rust

This is needed as the basis for the readlink -f option. Signed-off-by: Ben Hutchings <ben at decadent.org.uk> --- --- a/usr/include/stdlib.h +++ b/usr/include/stdlib.h @@ -92,4 +92,6 @@ static __inline__ int grantpt(int __fd) return 0; /* devpts does this all for us! */ } +__extern char *realpath(const char *, char *); + #endif /* _STDLIB_H */ --- a/usr/klibc/Kbuild +++

This is needed as the basis for the readlink -f option. Signed-off-by: Ben Hutchings <ben at decadent.org.uk> --- v2: Don't implement the BSD/GNU extension of allowing a non-existent last part. Use open(O_PATH) and procfs to get resolved name from the kernel. --- a/usr/include/stdlib.h +++ b/usr/include/stdlib.h @@ -92,4 +92,6 @@ static __inline__ int grantpt(int __fd) return

Commit-ID: 3fefc6a404a970a911417d0345618a7e9abfef70 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=3fefc6a404a970a911417d0345618a7e9abfef70 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Wed, 6 Jan 2016 00:43:25 +0000 Committer: H. Peter Anvin <hpa at linux.intel.com> CommitDate: Tue, 5 Jan 2016 17:45:36 -0800 [klibc] MIPS: Update archfcntl.h

On Mon, July 13, 2020 10:23, Andrea Venturoli wrote: > On 2020-07-13 15:06, James B. Byrne wrote: > >>> Just out of curiosity, are you also using vfs_zfsacl? >> >> Yes. > > But only on DC1, AFAICT! > I see no mention of it on DC2's smb.conf. > That could be the reason why you have two different behaviour. > > bye > av. > That appears to