[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1831354] Re: unable to read symlinks when mounting 9p filesystem wi
From: |
Thomas Huth |
Subject: |
[Bug 1831354] Re: unable to read symlinks when mounting 9p filesystem with security_model=mapped |
Date: |
Wed, 05 May 2021 11:45:42 -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/173
** Changed in: qemu
Status: New => Expired
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #173
https://gitlab.com/qemu-project/qemu/-/issues/173
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1831354
Title:
unable to read symlinks when mounting 9p filesystem with
security_model=mapped
Status in QEMU:
Expired
Bug description:
I am trying to use clang that is mounted from a 9p filesystem that has the
options
-fsdev local,id=virtfs3,path=/clang,security_model=mapped-file -device
virtio-9p-pci,fsdev=virtfs3,mount_tag=clang
clang has symlinks to clang-9. eg /clang/clang/bin/clang is a symlink
that points to clang-9 in the current directory.
the clang filesystem is on a bind mount point on /clang/clang on the
host and this is mapped to the same place on the guest. If I have the
same virtfs mount point with the security_model=none I don't have this
problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1831354/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug 1831354] Re: unable to read symlinks when mounting 9p filesystem with security_model=mapped,
Thomas Huth <=