Date: Tue, 30 May 2023 16:59:29 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 271704] O_PATH and acl_get_fd_np doesn't work on FreeBSD 13(.2) and causes vfs_zfsacl in Samba to fail Message-ID: <bug-271704-227-DTJzbjaoto@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-271704-227@https.bugs.freebsd.org/bugzilla/> References: <bug-271704-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D271704 --- Comment #7 from Peter Eriksson <pen@lysator.liu.se> --- > Samba must be doing something else there for Linux. Yes, Linux doesn't support accessing local real ZFS ACLs at all...=20 I think you might sort of work around that by NFSv4-exporting a ZFS filesys= tem and then loopback mount it back onto the same host, since ZFS-on-Linux internally does support the full ACLs (and exposes them via NFS as 'xattrs'= so you can modify them via that interface - there just isn't a working kernel - userland interface to access/modify them directly. There is some half-baked PosixACL emulation support in ZFS-on-Linux but that only supports a subset = of the full access rights. So the Samba vfs_zfsacl module only works on FreeBSD (and Solaris-derivates) One (out of many, but that one is a showstopper for us) big reason we use FreeBSD and not Linux as the OS for our ZFS-based fileservers :-) ZFS on Linux isn't that big either so people using Samba on Linux are norma= lly using other filesystems that doesn't have "full" ZFS/NFS ACLs either and th= en they emulate the ACLs using other means (but that makes it hard to share da= ta between SMB and NFS for example since Samba will validate ACLs one way and = then the kernel/NFS will do it differently). It's big headache. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-271704-227-DTJzbjaoto>