From: Vivek Goyal <vgoyal@redhat.com>
To: Colin Walters <walters@verbum.org>
Cc: Sergio Lopez <slp@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
virtio-fs-list <virtio-fs@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Virtio-fs] virtiofsd: Any reason why there's not an "openat2" sandbox mode?
Date: Thu, 29 Sep 2022 10:10:05 -0400 [thread overview]
Message-ID: <YzWnPZ5Y6ivS8e1v@redhat.com> (raw)
In-Reply-To: <b963f623-aa85-4285-9bfa-5fcb4744c354@app.fastmail.com>
On Thu, Sep 29, 2022 at 10:04:36AM -0400, Colin Walters wrote:
> On Wed, Sep 28, 2022, at 3:28 PM, Vivek Goyal wrote:
>
> > Sounds reasonable. In fact, we could probably do someting similar
> > for "landlock" as well.
>
> Thanks for the discussion all! Can someone (vaguely) commit to look into this in say the next few months? It's not *urgent*, we can live with the 9p flakes and problems short term, just trying to figure out if this needs to be on our medium-term radar or not. Thanks!
Hi Colin,
What's your use case. How do you plan to use virtiofs.
Thanks
Vivek
next prev parent reply other threads:[~2022-09-29 14:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 21:24 virtiofsd: Any reason why there's not an "openat2" sandbox mode? Colin Walters
2022-09-27 16:37 ` [Virtio-fs] " Vivek Goyal
2022-09-27 16:37 ` Vivek Goyal
2022-09-27 16:57 ` [Virtio-fs] " Vivek Goyal
2022-09-27 16:57 ` Vivek Goyal
2022-09-27 17:27 ` [Virtio-fs] " German Maglione
2022-09-27 17:27 ` German Maglione
2022-09-27 17:51 ` [Virtio-fs] " Colin Walters
2022-09-27 17:51 ` Colin Walters
2022-09-27 20:14 ` [Virtio-fs] " Stefan Hajnoczi
2022-09-28 8:33 ` Sergio Lopez
2022-09-28 19:28 ` Vivek Goyal
2022-09-29 14:04 ` Colin Walters
2022-09-29 14:10 ` Vivek Goyal [this message]
2022-09-29 15:47 ` Colin Walters
2022-09-29 17:03 ` Vivek Goyal
2022-09-30 8:13 ` German Maglione
2022-10-03 22:51 ` Colin Walters
2022-10-05 21:29 ` Vivek Goyal
2022-09-28 19:26 ` Vivek Goyal
2022-09-28 19:26 ` Vivek Goyal
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=YzWnPZ5Y6ivS8e1v@redhat.com \
--to=vgoyal@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=slp@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtio-fs@redhat.com \
--cc=walters@verbum.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.