From: Vivek Goyal <vgoyal@redhat.com>
To: virtio-fs-list <virtio-fs@redhat.com>
Subject: [Virtio-fs] Vivek's Status (Week starting 5th August, 2019)
Date: Fri, 9 Aug 2019 15:27:08 -0400 [thread overview]
Message-ID: <20190809192708.GA2431@redhat.com> (raw)
virtio_fs
=========
- Fixed bunch of issues and rebased virtio_fs patches to 5.3-rc kernel
and pushed to private branch.
https://github.com/rhvgoyal/linux/commits/vivek-5.3-aug-07-2019
- Took care of some of the issues Liu Bo pointed in virtio_fs.
https://github.com/rhvgoyal/linux/commit/0434504ec11dc2b884939b32d6dde6c9c92def94
https://github.com/rhvgoyal/linux/commit/127e2551f263a0cc7c6a4f18cbbd55693dfee4d9
- Reviwed ftrace event patch for virtio_fs.
https://www.redhat.com/archives/virtio-fs/2019-August/msg00072.html
- Bunch of other activity on virtio-fs list.
https://www.redhat.com/archives/virtio-fs/2019-August/msg00103.html
https://www.redhat.com/archives/virtio-fs/2019-August/msg00080.html
https://www.redhat.com/archives/virtio-fs/2019-August/msg00074.html
https://www.redhat.com/archives/virtio-fs/2019-August/msg00054.html
https://www.redhat.com/archives/virtio-fs/2019-August/msg00044.html
Containers + Overlayfs
======================
- Spent some time debugging the overlayfs issue Dan Walsh pointed to where
mounter does not have CAP_DAC_OVERRIDE and then chmod fails.
https://github.com/containers/libpod/issues/3684#issuecomment-519574675
- Looked into the issue of overlayfs not working on top of virtio-fs.
https://github.com/kata-containers/runtime/issues/1888#issuecomment-518259095
next reply other threads:[~2019-08-09 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 19:27 Vivek Goyal [this message]
2019-08-12 12:48 ` [Virtio-fs] Vivek's Status (Week starting 5th August, 2019) 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=20190809192708.GA2431@redhat.com \
--to=vgoyal@redhat.com \
--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 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.