On Tue, Jan 24, 2017 at 07:53:06PM -0700, Chris Murphy wrote: > On Tue, Jan 24, 2017 at 3:50 PM, Omar Sandoval <osandov@xxxxxxxxxxx> wrote: > > > Got this to repro after installing systemd-container. It's happening on > > lsetxattr() to set the SELinux context on /var/lib/machines, which is a > > subvolume. Looking into it now. Thanks for all of the help, Chris. > > Aha! So the snapshot part was a goose chase, it has nothing to do with > that, really. Because I'm taking a snapshot of root, the nested > /var/lib/machines subvolume is not in that snapshot, so now it has to > be created by systemd at next boot and the proper selinux label set on > it. > > It means there's something different about subvolumes and directories > when it comes to xattrs, and the xattr patch I found in bisect is > exposing the difference, hence things getting tripped up. The snapshots were actually the key -- the error was because setxattr() was being allowed on the read-only directory created in the place of the /var/lib/machines subvolume. Not sure if you saw the patch I sent up, but this should fix it: https://patchwork.kernel.org/patch/9536307/ -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
