From: virtiofs-bot@sinrega.org
To: virtio-fs@redhat.com
Subject: [Virtio-fs] [virtiofsd] Issue opened: sandbox issue when merging virtiofsd and Cloud-hypervisor
Date: Wed, 12 Oct 2022 07:09:27 +0000 (UTC) [thread overview]
Message-ID: <28559.122101203092500145@us-mta-272.us.mimecast.lan> (raw)
Hi team,
Because of my use case, I'm merging virtiofsd to cloud-hypervisor, so that they are in one process. But I met a issue about the sandbox mode.
because virtiofsd are several threads after merging, I cannot use sandbox=namespace or sandbox=chroot since that causes forking a new process.
And if I force it not to do fork but apply new namespace to the current process, that also changes the namespace of the cloud-hypervisor since
the namespace setting is process-wide not thread-wide.
Any idea to address this issue, is it safe to run virtiofsd in sandbox=none mode?
---
https://gitlab.com/virtio-fs/virtiofsd/-/issues/63
reply other threads:[~2022-10-12 7:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=28559.122101203092500145@us-mta-272.us.mimecast.lan \
--to=virtiofs-bot@sinrega.org \
--cc=virtio-fs@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).