[Bug 1500265] Re: nested 9p filesystem with security_model=mapped-xattr

[Christian Schoenebeck]

The status of this issue is unchanged in QEMU, i.e. user.virtfs.* is
still filtered out.

If someone wants to see this changed, please use the common way for sending the 
patch via ML:
https://wiki.qemu.org/Contribute/SubmitAPatch

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1500265

Title:
  nested 9p filesystem with security_model=mapped-xattr

Status in QEMU:
  Incomplete

Bug description:
  I do not know whether this is a bug or a feature request, but on a 9p
  virtfs with security_model=mapped-xattr, access to extended attributes
  starting with "user.virtfs" coming from the guest seem to be silently
  ignored. Would it not be more correct to use some sort of "escaping",
  say map to "user.virtfs.x" on guest to "user.virtfs.virtfs.x" on host
  or something like that, so that the guest can use arbitrary
  attributes.

  In particular, this would allow nested virtual machines to use nested
  9p virtfs with security_model=mapped-xattr.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1500265/+subscriptions