[Bug 9594] New: Error transferring user and non-user xattr using --fake-super under Linux

[samba-bugs at samba.org]

https://bugzilla.samba.org/show_bug.cgi?id=9594

           Summary: Error transferring user and non-user xattr using
                    --fake-super under Linux
           Product: rsync
           Version: 3.1.0
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
        AssignedTo: wayned at samba.org
        ReportedBy: succinic.anhydride at yahoo.com
         QAContact: rsync-qa at samba.org


Overview:
I'm using rsync -aX as root on the sender (local) and --fake-super on the
receiver (remote) to preserve attributes. I'm using version 3.1.0dev as I
needed a solution to Bug 8201
(https://bugzilla.samba.org/show_bug.cgi?id=8201). I get the error "could not
find xattr #1 for [foo]" when trying to transfer a file that has both a
non-user extended attribute with a long string value AND a user extended
attribute where the name of the user EA preceeds "user.rsync" in lexical sort
order. The error is triggered only if the transfer is remote AND rsync is run
as root on the local/sender side so both non-user and user attrs are
transferred.

Steps to reproduce:
1. sudo touch foo
2. sudo setfattr -n user.rsx -v "1" foo ## user.rsx sorts before user.rsync
3. sudo setfattr -n security.selinux -v "system_u:object_r:cachefiles_var_t:s0"
foo ## non-user EA with a long string value
5. sudo rsync -i -aOzAX --numeric-ids --rsync-path="rsync --fake-super" foo
user at remote:/tmp/ ## user does not have root access on host remote

Actual Results:
  <f+++++++++ foo
  [receiver] could not find xattr #1 for foo
  rsync error: protocol incompatibility (code 2) at xattrs.c(620)
[receiver=3.1.0dev]

Expected Results: no error, file and xattrs transferred successfully

System details:
Local/sender and remote/receiver are RHEL 6.3 with rsync 3.1.0dev

-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.