[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1500265] Re: nested 9p filesystem with security_model=mapped-xattr
From: |
Thomas Huth |
Subject: |
[Bug 1500265] Re: nested 9p filesystem with security_model=mapped-xattr |
Date: |
Tue, 04 May 2021 07:23:01 -0000 |
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/117
** Changed in: qemu
Status: Triaged => Expired
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #117
https://gitlab.com/qemu-project/qemu/-/issues/117
--
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:
Expired
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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug 1500265] Re: nested 9p filesystem with security_model=mapped-xattr,
Thomas Huth <=