similar to: rsync xattr support doesn't play nice with selinux

I'm writing a stackable file system and one of it's features is that it can combine many sparse files into a single view. On ext2/3 I was using bmap to give me the information needed, so for instance, if I created a big sparse file and tacked on some information at the end on ext2/3 I'd get something like blade12:~# ~/a.out abc File: abc Size: 30002 Blocks: 8 Blocksize: 4096 0

Thanks for the help on the missing '-p1' for the acl and xattr patches. Things are configuring and making properly now. However, I couldn't help noticing this during the configure: checking whether to support ACLs... ACLs requested -- running tests checking for acl_get_file in -lacl... no checking for ACL support... yes checking ACL test results... Using posix ACLs checking for

https://bugzilla.samba.org/show_bug.cgi?id=5939 Summary: rsync: delete of stat xattr failed for ... (in backup): Operation not permitted (1) Product: rsync Version: 3.0.4 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

The proper file that should be included is `sys/xattr.h` as that comes from `glibc` and not `attr/xattr.h` which ships with the `attr` utility. New enough `attr` utility (at least 2.4.48 in my case) even includes a #warning in `attr/xattr.h` for projects that still have this mistake in the code. --- daemon/xattr.c | 8 ++------ fuse/test-fuse.c | 4 ---- lib/fuse.c |

If the system supports selinux, we will return sucessfully from ocfs2_init_security_get if it is called for the mount point. And in that case if the volume doesn't have xattr support, we will not be able to create a new inode in the mount dir because ocfs2_mknod will try to set security attributes for a new created inode. This patch check xattr support in ocfs2_init_security_get, so it will

Hi, I have recently downloaded the rsync-3.0.0pre5 and wanted to see how it works (especially xattr feature).. I did following steps.. ./configure make make test make test shows following tests skipped.. SKIP xattrs (Unable to set an xattr) from 3.0 i have read that xattr support is by default and there is no specific patch is required to use this feature.. I want to know how the xattr

This patch set a gap (4 bytes) between xattr entry and name/value when xattr in bucket. This gap use to seperate entry and name/value when a bucket is full. It had already been set when xattr in inode/block. Signed-off-by: Tiger Yang <tiger.yang at oracle.com> --- fs/ocfs2/xattr.c | 18 ++++++++++-------- 1 files changed, 10 insertions(+), 8 deletions(-) diff --git a/fs/ocfs2/xattr.c

In ocfs2_value_metas_in_xattr_header, we should Use le16_to_cpu for ocfs2_extent_list.l_next_free_rec. Signed-off-by: Tao Ma <tao.ma at oracle.com> --- fs/ocfs2/xattr.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/fs/ocfs2/xattr.c b/fs/ocfs2/xattr.c index fe34190..8c0bfa2 100644 --- a/fs/ocfs2/xattr.c +++ b/fs/ocfs2/xattr.c @@ -6066,7 +6066,7 @@ static int

Tristan, could you please run your xattr test against it? xs->base used to be allocated a 4K size and all the contents in the bucket are copied to the it. So in ocfs2_xattr_bucket_set_value_outside, we are safe to use xs->base + offset. Now we use ocfs2_xattr_bucket to abstract xattr bucket and xs->base is initialized to the start of the bu_bhs[0]. So xs->base + offset will overflow

Move all the common code to a new _getxattr function, much like done for other xattrs operations. Mostly code motion, no functional changes. --- daemon/xattr.c | 54 +++++++++++------------------------------------------- 1 file changed, 11 insertions(+), 43 deletions(-) diff --git a/daemon/xattr.c b/daemon/xattr.c index abed5ff..d8ad59a 100644 --- a/daemon/xattr.c +++ b/daemon/xattr.c @@ -55,6

Inlined xattr shared free space of inode block with inlined data or data extent record, so the size of the later two should be adjusted when inlined xattr is enabled. See ocfs2_xattr_ibody_init(). But this isn't done well when reflink. For inode with inlined data, its max inlined data size is adjusted in ocfs2_duplicate_inline_data(), no problem. But for inode with data extent record, its

Folks, To keep track of what we want to upstream in the 2.6.28-rc cycle, I've put together a branch called 'xattr-28' with almost all of the patches merged. You can see it and pull it from my linux-2.6.git repository. View: http://oss.oracle.com/git/?p=jlbec/linux-2.6.git;a=shortlog;h=xattr-28 Pull: git://oss.oracle.com/git/jlbec/linux-2.6.git xattr-28 The branch contains the

Hi, gcc 4.4.1 generates the following build warning on i386: CC [M] fs/ocfs2/xattr.o fs/ocfs2/xattr.c: In function ???ocfs2_xattr_block_get???: fs/ocfs2/xattr.c:1055: warning: ???block_off??? may be used uninitialized in this function The following fix is based on a similar approach by David Howells few days back: http://lkml.org/lkml/2009/7/9/109, Signed-off-by: Subrata Modak<subrata at

On 6/30/07, Wayne Davison <wayned@samba.org> committed: > Added Files: > checksum-xattr.diff > Log Message: > A simple patch that lets rsync use cached checksum values stored in > each file's extended attributes. A perl script is provided to create > and update the values. Wayne, You should be aware of two drawbacks of caching checksums in xattrs: First,

Hello I am trying to integrate OS X 10.10.4 clients into existing Samba infractructure run by our IT department. We are currently using Samba 4.2.3. File share is stored on iSCSI array with ext4 filesystem which should support both ACL and XATTR. We are trying to setup vfs_fruit module to avoid possible performance problems on OS X clients. We do NOT user netatalk. Current vfs_fruit config:

Does rsync support acl and xattr (as with acl and user_xattr mount options)? I saw some acl patches for rsync, so probably it's not officially blessed yet. However, I didn't see any xattr patches - although some talks about it on the list go back into year 2003. So how it is with support for these? If I backup a Samba server, which has a filesystem mounted with acl,user_xattr (with

Applying the xattr and acl patch to 2.6.9, running ./prepare-source and config with ./configure --enable-xattr-support results in a version which fails to transfer with the error msg 'wrong write used in receiver' and complaints about protocol mismatch. I see there's a patch for a similar problem when SUPPORT_ACLS is defined; anybody done one for --xattrs? No, I'm not

Modification from V2 to V3: Use a more pefect code suggested by Joel. Thank Joel for it. In ocfs2/xattr, we must make sure the xattrs which have the same hash value exist in the same bucket so that the search schema can work. But in the old implementation, when we want to extend a bucket, we just move half number of xattrs to the new bucket. This works in most cases, but if we are lucky enough we

Am I wrong to believe that pxelinux can't use syslinux configurtion files as is? I have a syslinux/isolinux setup that works fine in those environments, lets me boot a root file system based on different criteria. However, when I moved it over to pxelinux, i'm able to have it get an ip address over dhcp, fetch pxelinux.0 over tftp and seemingly fetch 'default' from

On Thu, 2022-12-01 at 11:41 +0100, Roberto Sassu wrote: > From: Roberto Sassu <roberto.sassu at huawei.com> > > Currently, evm_inode_init_security() processes a single LSM xattr from > the array passed by security_inode_init_security(), and calculates the > HMAC on it and other inode metadata. > > Given that initxattrs() callbacks, called by >