From: Amir Goldstein <amir73il@gmail.com>
To: Aleksa Sarai <asarai@suse.de>
Cc: Linux Containers <containers@lists.linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Josh Triplett <josh@joshtriplett.org>,
overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: Overlayfs @Plumbers
Date: Sun, 30 Aug 2020 14:44:20 +0300 [thread overview]
Message-ID: <CAOQ4uxisYp9nGacXL8LaLiGa2ciXWOHYxgda-G0QEaw9t0MZHw@mail.gmail.com> (raw)
In-Reply-To: <20200828155849.k46uk3x63aio3g3o@yavin.dot.cyphar.com>
On Fri, Aug 28, 2020 at 6:58 PM Aleksa Sarai <asarai@suse.de> wrote:
>
> On 2020-08-28, Eric W. Biederman <ebiederm@xmission.com> wrote:
> > Amir Goldstein <amir73il@gmail.com> writes:
> >
> > > Hi Guys,
> > >
> > > It's been nice to virtually meet with you yesterday.
> > > Some of you wanted to follow up on overlayfs related issues.
> > >
> > > If you want to discuss, try to find me in one of the
> > > https://meet.2020.linuxplumbersconf.org/hackrooms
> > > today between 16:00-17:00 UTC
> > > (No need to enter the room to see who's inside)
> > >
> > > If those times do not work for you, contact me and we can try
> > > to schedule another time.
> >
> > Did this conversation wind up happening? Do we need to reschedule?
>
> This conversation already happened in a Hackroom on Tuesday. I'm not
> sure if the Hackrooms will have their recordings published, so maybe
> Amir can post any of the takeaways we had?
>
AFAIK we had discussed two issues.
1. Watching changes on upper layer
2. OCI format v2
#1 was brought up by Josh Triplett.
He asked whether watching changes using inotify/fanotify on upper dir
and reading changes from upper dir is a reasonable practice.
I suggested that he use fanotify filesystem mark to watch changes
on overlay sb and read the changes from overlay mount.
#2 TBH I lost track and you guys continued the discussion after I left.
From what I gathered we need a way to describe clones and renames
more efficiently, but I did not hear any solid plan of how to do that.
So perhaps you would be able to fill in some details here.
Thanks,
Amir.
_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/containers
prev parent reply other threads:[~2020-08-30 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOQ4uxjXZdXZAaeiJ_p9n7NJziBv2yvWqSDs0hDd1ONUrVKxOQ@mail.gmail.com>
2020-08-28 15:33 ` Overlayfs @Plumbers Eric W. Biederman
2020-08-28 15:58 ` Aleksa Sarai
2020-08-29 15:40 ` Sargun Dhillon
2020-08-30 11:29 ` Giuseppe Scrivano
2020-08-30 11:37 ` Amir Goldstein
2020-08-30 11:44 ` Amir Goldstein [this message]
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=CAOQ4uxisYp9nGacXL8LaLiGa2ciXWOHYxgda-G0QEaw9t0MZHw@mail.gmail.com \
--to=amir73il@gmail.com \
--cc=asarai@suse.de \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=josh@joshtriplett.org \
--cc=linux-unionfs@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).