From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: linux-unionfs@vger.kernel.org
Cc: miklos@szeredi.hu, amir73il@gmail.com
Subject: Re: [PATCH V3] ovl: Allocate anonymous devs for lowerdirs
Date: Thu, 27 Jul 2017 11:54:15 +0530 [thread overview]
Message-ID: <2098530.dS0XS0MFtf@localhost.localdomain> (raw)
In-Reply-To: <20170724091722.23252-1-chandan@linux.vnet.ibm.com>
On Monday, July 24, 2017 2:47:22 PM IST Chandan Rajendra wrote:
> For stat(2) on lowerdir non-dir entries in non-samefs case, this commit
> provides unique values for st_dev. The unique values are obtained by
> allocating anonymous bdevs for each of the lowerdirs in the overlayfs
> instance.
>
> Signed-off-by: Chandan Rajendra <chandan@linux.vnet.ibm.com>
> ---
> Changelog:
>
> v2->v3: Optimize away O(n) search for pseudo dev in ovl_get_pseudo_dev().
>
> v1->v2: Drop code that provided unique st_dev across copy up.
>
I have rebased Amir's "ovl: relax same fs constrain for constant st_ino"
patch on top of the changes made in this patch. The tree containing
the rebased patch can be found at
"https://github.com/chandanr/linux.git rework-anonymous-dev"
I have tested this by executing unionmount-testsuite's "./run --ov --verify".
--
chandan
next prev parent reply other threads:[~2017-07-27 6:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 11:01 [PATCH V2] ovl: Allocate anonymous devs for lowerdirs Chandan Rajendra
2017-06-23 13:34 ` Amir Goldstein
2017-06-23 13:42 ` Chandan Rajendra
2017-06-27 7:31 ` Chandan Rajendra
2017-06-27 9:04 ` Amir Goldstein
2017-06-30 10:58 ` Chandan Rajendra
2017-06-30 14:50 ` Amir Goldstein
2017-07-14 9:38 ` Miklos Szeredi
2017-07-15 14:27 ` Chandan Rajendra
2017-07-24 9:17 ` [PATCH V3] " Chandan Rajendra
2017-07-27 6:24 ` Chandan Rajendra [this message]
2017-09-21 17:46 ` Amir Goldstein
2017-09-22 2:40 ` Chandan Rajendra
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=2098530.dS0XS0MFtf@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;
as well as URLs for NNTP newsgroup(s).