Bug 1038302

In case it matters this is how the fileystems are mounted:
  tmpfs on /tmp type tmpfs (rw,seclabel)
  /dev/xxx on /tmp/F20-root type xfs (rw,relatime,seclabel,attr2,inode64,noquota)

I've also done an experiment with tar:

    [root@f19 backup]# tar -c -f - --acls --selinux \
            --xattrs --xattrs-include='*' \
            -C /tmp/F20-root \
            /usr/lib/systemd/system/sshd-keygen.service | \
        tar -x -f - --acls --selinux \
            --xattrs --xattrs-include='*' \
            -C /tmp/backup/dst
    tar: Removing leading `/' from member names
    [root@f19 backup]# ls -lZ /tmp/backup/dst/usr/lib/systemd/system/sshd-keygen.service
    -rw-r--r--. root root system_u:object_r:sshd_unit_file_t:s0 /tmp/backup/dst/usr/lib/systemd/system/sshd-keygen.service

The programs that I'm using are:
rsync-3.0.9-12.fc19.x86_64
tar-1.26-27.fc19.x86_64

Adding the maintainer of rsync in case this is an issue with rsync.

unlabeled_t is a misnamed type, it should be unknown_label_t, or something like that.  Basically it means that a file has a label that the kernel does not understand and you are bing blocked from putting that label on the file system.

Now I understand better what's going on, but there are still a SELinux
denial and a rsync error.

Lets change this existing rule:

allow unlabeled_t fs_t:filesystem associate;

to

allow unlabeled_t xattrfs:filesystem associate;

and associate the xattrfs type attribute with all filesystem types that support extended attributes

SELinux must be able to failover on any filesystem that supports xattrs.

Its perfectly conceivable that for example a file on /run (which is on a tmpfs_t filesystem) becomes invalid at runtime. SELinux must be able to failover, and be able to associate unlabeled_t with that file

There are some more less likely scenarios i suspect like for example sysfs, securityfs, i guess any file system that supports extended attributes.

Point i am trying to make here: SELinux must be able to failover.

I agree.

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.