search for: xattr_name

Displaying 8 results from an estimated 8 matches for "xattr_name".

Did you mean: attr_name
2020 Jun 05
2
Extended attributes not working on mac
these lines were an option before but have already been marked as comments in my config. same behaviour as before, color tag shows for round about a second and disappears suddenly. Martin > Am 05.06.2020 um 09:23 schrieb Ralph Boehme via samba <samba at lists.samba.org>: > > Am 6/5/20 um 8:33 AM schrieb Martin Steiner / 3MF GmbH: >> Any more ideas? It?s not displaying
2020 Jun 05
2
Extended attributes not working on mac
...dirptr_get_entry) smbd_dirptr_get_entry mask=[Ohne Titel 15.txt] found Ohne Titel 15.txt fname=Ohne Titel 15.txt (Ohne Titel 15.txt) [2020/06/05 11:07:14.017343, 10, pid=51807, effective(1000, 1000), real(1000, 0), class=vfs] ../../source3/modules/vfs_streams_xattr.c:127(streams_xattr_get_name) xattr_name: user.DosStream.AFP_AfpInfo:$DATA, stream_name: :AFP_AfpInfo [2020/06/05 11:07:14.017460, 2] ../../source3/smbd/dosmode.c:136(unix_mode) unix_mode(Ohne Titel 15.txt) inheriting from . [2020/06/05 11:07:14.017476, 2] ../../source3/smbd/dosmode.c:162(unix_mode) unix_mode(Ohne Titel 15.txt) inhe...
2018 Apr 09
2
Operation Not Supported error for GETXATTR when VFS plugin "nfs4acl_xattr" is used
...now failing with access denied. Here is what I tried: *[root at test3 ajain]# net conf showshare local[local] path = /home/ajain/mount comment = local share guest ok = no read only = no hosts allow = ALL vfs objects = nfs4acl_xattr* * nfs4acl_xattr:xattr_name = system.nfs4_acl nfs4acl_xattr:encoding = xdr* I added/enabled some debug messages and here is what I see for XDR type: *[2018/04/09 21:53:34.024425, 3, pid=32098, effective(1101151, 1100513), real(1101151, 0)] ../source3/smbd/trans2.c:2667(call_trans2findfirst) call_trans2findf...
2018 Apr 05
4
Operation Not Supported error for GETXATTR when VFS plugin "nfs4acl_xattr" is used
...self, if I change the path to actual directory instead of ".", it still fails with same error. Can someone help me understand, why following call may fail when the path is locally mounted NFS share and not a VFS path: * length = SMB_VFS_NEXT_GETXATTR(handle, path, NFS4ACL_XATTR_NAME, blob.data, blob.length);* Since next module in the stack is Default_VFS, isn't it supposed to forward the request to local NFS client? I do not see any packets on NFS port of the local NFS client when this operation fails. Setup information: Samba Version: 4.6.2 CentOS Linux release 7.2.15...
2018 Apr 06
2
Operation Not Supported error for GETXATTR when VFS plugin "nfs4acl_xattr" is used
...> > Hi All > > > > > > > > I found there is one bug in the plugin. The name of the attribute for ACL as > > > > per strace output of nfs4_setfacl is system.nfs4_acl. > > > > The source code has defined it as > > > > #define NFS4ACL_XATTR_NAME      ( "system.nfs4acl" ) > > > > > > > > Note there is missing underscore. > > > > > > > > After this, the EOPNOTSUPP error is not observed. > > > > > > > > Hope this helps > > > > > > Hmmm. Thi...
2022 Dec 01
8
[PATCH v7 0/6] evm: Do HMAC of multiple per LSM xattrs for new inodes
From: Roberto Sassu <roberto.sassu at huawei.com> One of the major goals of LSM stacking is to run multiple LSMs side by side without interfering with each other. The ultimate decision will depend on individual LSM decision. Several changes need to be made to the LSM infrastructure to be able to support that. This patch set tackles one of them: gives to each LSM the ability to specify one
2012 Oct 12
9
[PATCH] Fits: tool to parse stream
...PE_INT }, + { "MODE", TYPE_OCTAL }, + { "UID", TYPE_INT }, + { "GID", TYPE_INT }, + { "RDEV", TYPE_HEX }, + { "CTIME", TYPE_TIME }, + { "MTIME", TYPE_TIME }, + { "ATIME", TYPE_TIME }, + { "OTIME", TYPE_TIME }, + { "XATTR_NAME", TYPE_STRING }, + { "XATTR_DATA", TYPE_BINARY }, + { "PATH", TYPE_STRING }, + { "PATH_TO", TYPE_STRING }, + { "PATH_LINK", TYPE_STRING }, + { "FILE_OFFSET", TYPE_INT }, + { "DATA", TYPE_LEN_ONLY }, + { "CLONE_UUID", TYPE_BI...
2023 Mar 14
7
[PATCH v8 0/6] evm: Do HMAC of multiple per LSM xattrs for new inodes
From: Roberto Sassu <roberto.sassu at huawei.com> One of the major goals of LSM stacking is to run multiple LSMs side by side without interfering with each other. The ultimate decision will depend on individual LSM decision. Several changes need to be made to the LSM infrastructure to be able to support that. This patch set tackles one of them: gives to each LSM the ability to specify one