fuse doesn't use security_inode_init_security?
chirantan at chromium.org
Thu May 7 07:53:13 UTC 2020
On Sat, May 2, 2020 at 12:46 AM Vivek Goyal <vgoyal at redhat.com> wrote:
> I am wondering how would fuse initialize the security context of newly
> created file. One way seems to be that it passes that information
> as part of FUSE_CREATE/FUSE_MKNOD calls to server and server sets
> its "fscreate" accordingly and then creates new file. This is similar
> to virtiofsd changing its effective uid/gid to the fuse client so that
> file is created with caller's uid/gid. Seems to be selinux context for
> file creation probably should be handled similiarly.
How would the fuse driver get the correct context without going
> Other method could be to first create new file and then new fuse
> commands to do setxattrs. But that will be racy as file will have
> some default label for sometime between creation and setxattr.
> Having said that, I have a question. How do you reconcile host selinux
> policy and guest selinux labels. I am assuming host selinux policy
> will have to know about guest labels so that it allows virtiofsd do
> set those labels? Dan, you might have more thoughts on this.
My understanding is that we currently merge the guest and host
policies so that all types in the guest are available on the host.
The host itself uses selinux in permissive mode. The top-level
directory is also owned exclusively by the guest and host processes
don't have access to it.
On Sat, May 2, 2020 at 3:32 AM Stephen Smalley
<stephen.smalley.work at gmail.com> wrote:
> (cc selinux list)
> security_inode_init_security() calls the initxattrs callback to
> actually set each xattr in the backing store (if any), so unless you
> have a way to pass that to the daemon along with the create request
> the attribute won't be persisted with the file. Setting the xattrs is
> supposed to be atomic with the file creation, not a separate
> setxattr() operation after creating the file, similar to ACL
> inheritance on new files.
But it's not truly atomic, is it? The underlying file system creates
the inode and then the inode_init_security selinux hook actually sets
the attributes. What would happen if the computer lost power after
the file system driver created the inode but before the selinux hook
set the attributes?
> Also possibly related
Interesting. Let me pull out the relevant bits and respond inline.
> - deadlock during mount with userspace waiting for mount(2) to complete
> and the kernel blocked on requesting the security.selinux xattr of the
> root directory as part of superblock setup during mount
I haven't personally run into this. It Just Works, except for the
> - there was an attempt to introduce distinctions based on filesystem
> "subtype" so that whitelisted fuse filesystems could have xattr support
> enabled when it was known that their userspace would handle mount(2)
> safely  but this was apparently always broken and later reverted .
I think we kind of side-stepped this issue. The fstype for virtiofs
is "virtiofs" instead of something like "fuse.virtiofs" so there is no
subtype handling required.
> - there is the issue of trusting the fuse filesystem for its labeling
> information and for domain/context transitions
This is definitely an issue for regular fuse file systems. However,
the virtiofs device has read/write access to all the VM's memory so
there isn't much the VM can do if it doesn't trust the device.
I guess what I'm trying to understand is: what are the issues with
having the fuse driver call the inode_init_security hooks? Even if
it's not something that can be turned on by default in mainline, I'd
like to evaluate whether we can turn it on locally in our restricted
One issue is the lack of atomicity guarantees. This is likely a
deal-breaker for general fuse usage. However, I don't think it's an
issue for our restricted use of virtiofs because the attributes will
be set "atomically" from the guest userspace's perspective. It won't
be atomic on the host side, but host processes don't have access to
those directories anyway.
Are there any other issues?
More information about the Linux-security-module-archive