From: Olie Hilt <1831354@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1831354] Re: unable to read symlinks when mounting 9p filesystem with security_model=mapped
Date: Sun, 02 Jun 2019 00:21:57 -0000 [thread overview]
Message-ID: <155943491760.16274.10660364226991324686.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 155943483504.16885.17011343834954742829.malonedeb@chaenomeles.canonical.com
On the host: readlink clang
clang-9
and guest:
ls: cannot read symbolic link 'clang': No such file or directory
lrwxrwxrwx 1 root root 7 May 30 02:21 clang
readlink clang
returns nothing.
--
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:
New
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
next prev parent reply other threads:[~2019-06-02 0:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-02 0:20 [Qemu-devel] [Bug 1831354] [NEW] unable to read symlinks when mounting 9p filesystem with security_model=mapped Olie Hilt
2019-06-02 0:21 ` Olie Hilt [this message]
2021-05-05 11:45 ` [Bug 1831354] " Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=155943491760.16274.10660364226991324686.malone@chaenomeles.canonical.com \
--to=1831354@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).