Bug #40648
Load catia VFS module before zfs_space and zfsacl
Description
Observed on customer system. Directories had ":" in them. Catia mapping of 0x3a:0xf022 did not allow access to directory because the ACL checks were happening prior to the catia mapping taking effect. This meant that Samba tried to get the ACL for a non-existent file "foo⋰bar" rather than "foo:bar".
Related issues
History
#1
Updated by John Hixson almost 3 years ago
Updated by John Hixson - Copied from Bug #34146: Load catia VFS module before zfs_space and zfsacl added
#2
Updated by John Hixson almost 3 years ago
11.1-stable PR: https://github.com/freenas/freenas/pull/1630
#3
Updated by Dru Lavigne almost 3 years ago
Updated by Dru Lavigne - Status changed from Unscreened to In Progress
- Needs QA changed from No to Yes
- Needs Merging changed from No to Yes
#4
Updated by Dru Lavigne almost 3 years ago
- Assignee changed from Andrew Walker to John Hixson
#5
Updated by Dru Lavigne almost 3 years ago
- Status changed from In Progress to Ready for Testing
- Needs Merging changed from Yes to No
#6
Updated by Michael Reynolds almost 3 years ago
Updated by Michael Reynolds - Status changed from Ready for Testing to Passed Testing
- Needs QA changed from Yes to No
Created a new dataset for the Samba share
went to Sharing:Windows -> Advanced
Under VFS Objects "selected" zfs_space, zfsacl, and catia
Setup/enabled and started the SMB service
via SSH I checked the module load order
cat /usr/local/etc/smb4.conf | grep 'vfs objects'
vfs objects = catia zfs_space zfsacl streams_xattr
catia is loaded before zfs_space and zfsacl (streams_xattr came by
default I think)
#7
Updated by Dru Lavigne almost 3 years ago
- Status changed from Passed Testing to Done