From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: miklos@szeredi.hu,
"linux-unionfs@vger.kernel.org" <linux-unionfs@vger.kernel.org>
Subject: Re: Overlayfs TODOs
Date: Wed, 17 May 2017 18:16:07 +0530 [thread overview]
Message-ID: <3385315.J8HfPLhZLT@localhost.localdomain> (raw)
In-Reply-To: <CAOQ4uxh+wpNX=Zc8AWOgy3EG5Nn_8omv7HZOgngyfGUY_AsFHA@mail.gmail.com>
On Wednesday, May 17, 2017 5:56:31 PM IST Amir Goldstein wrote:
> On Wed, May 17, 2017 at 2:42 PM, Chandan Rajendra
> <chandan@linux.vnet.ibm.com> wrote:
> >
> > I am keen on working on overlayfs. It would be very helpful if you could
> > provide me a list of Todo items associated with Overlayfs.
> >
>
> This is the TODO list that I maintain on wiki:
> https://github.com/amir73il/overlayfs/wiki/Overlayfs-TODO
>
> It includes at least most of the tasks that are in Miklos' head:
> https://marc.info/?l=linux-unionfs&m=149441099931390&w=2
>
> My focus right now is all the "non stared" tasks for "same fs" configuration,
> aiming for kernel 4.13.
>
> Is there are specific area of interest for you with overlayfs?
> Any specific configuration or use case? Or is the interest purely academic?
>
> I suppose you are looking to start of with smaller tasks?
>
> There is actually one task that should be very simple to do and can also
> bring large benefit for many users.
>
> In his pull request for kernel 4.12 Miklos writes:
> "The biggest part of this is making st_dev/st_ino on the overlay behave like a
> normal filesystem ... future work will move the general case towards more sane
> behavior."
> https://marc.info/?l=linux-unionfs&m=149442365202823&w=2
>
> The work towards constant st_dev/st_ino for the general case is not within my
> immediate scope of interest, but it shouldn't be hard. The basic idea was
> explained by Miklos here:
> https://marc.info/?l=linux-unionfs&m=149259338809700&w=2
>
Amir, I will work on this task. Thanks for the guidance.
>
>
> Cheers,
> Amir.
>
>
--
chandan
parent reply other threads:[~2017-05-17 12:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAOQ4uxh+wpNX=Zc8AWOgy3EG5Nn_8omv7HZOgngyfGUY_AsFHA@mail.gmail.com>]
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=3385315.J8HfPLhZLT@localhost.localdomain \
--to=chandan@linux.vnet.ibm.com \
--cc=amir73il@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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