On Wed, Feb 10, 2021 at 4:04 AM Dr. David Alan Gilbert (git)
wrote:
>
> From: "Dr. David Alan Gilbert"
> +
> +typedef struct {
> +/* Offsets within the file being mapped */
> +uint64_t fd_offset[VHOST_USER_FS_SLAVE_ENTRIES];
> +/* Offsets within the cache */
> +uint64_t c_offset[V
On Tue, Feb 2, 2021 at 3:22 AM Stefan Hajnoczi wrote:
> Hi Chirantan,
> I wanted to bring this CVE to your attention because the discussion has
> revealed a number of other issues (not necessarily security issues) in
> virtiofsd that may also be present in other virtio-fs daemon
> implementations.
On Thu, Oct 8, 2020 at 5:55 PM Stefan Hajnoczi wrote:
>
> virtiofsd cannot run in a container because CAP_SYS_ADMIN is required to
> create namespaces.
>
In crosvm we deal with this by also creating a user namespace, which
then allows us to create the mount, net, and pid namespaces as well.
Could
On Sat, Sep 19, 2020 at 6:36 AM Vivek Goyal wrote:
>
> Hi All,
>
> virtiofsd default thread pool size is 64. To me it feels that in most of
> the cases thread pool size 1 performs better than thread pool size 64.
>
> I ran virtiofs-tests.
>
> https://github.com/rhvgoyal/virtiofs-tests
>
> And here
On Thu, Jun 25, 2020 at 9:55 PM Vivek Goyal wrote:
>
> On Thu, Jun 25, 2020 at 12:19:39PM +0900, Chirantan Ekbote wrote:
> [..]
> > > Chirantan,
> > >
> > > So you ended up renaming all "trusted", "security" and "system" xattrs?
&
On Sat, Jun 20, 2020 at 4:15 AM Vivek Goyal wrote:
>
> On Fri, Jun 19, 2020 at 01:46:20PM +0900, Chirantan Ekbote wrote:
> > On Fri, Jun 19, 2020 at 4:27 AM Vivek Goyal wrote:
> > >
> > > On Thu, Jun 18, 2020 at 08:16:55PM +0100, Dr. David Alan Gilbert wro
On Fri, Jun 19, 2020 at 4:27 AM Vivek Goyal wrote:
>
> On Thu, Jun 18, 2020 at 08:16:55PM +0100, Dr. David Alan Gilbert wrote:
> > * Vivek Goyal (vgo...@redhat.com) wrote:
> > > On Thu, Apr 16, 2020 at 05:49:05PM +0100, Stefan Hajnoczi wrote:
> > > > virtiofsd doesn't need of all Linux capabilitie
On Fri, Jun 19, 2020 at 5:40 PM Dr. David Alan Gilbert
wrote:
>
> * Chirantan Ekbote (chiran...@chromium.org) wrote:
>
> > We ended up working around it by prefixing "user.virtiofs." to the
> > xattr name[2], which has its own problems but there was pretty much no
&
