From: Eryu Guan <eguan@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>, Xiong Zhou <xzhou@redhat.com>,
linux-unionfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 0/5] fstests: more tests for overlay constant inode numbers
Date: Fri, 28 Apr 2017 13:30:20 +0800 [thread overview]
Message-ID: <20170428053020.GK26397@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1493305775-12559-1-git-send-email-amir73il@gmail.com>
On Thu, Apr 27, 2017 at 06:09:30PM +0300, Amir Goldstein wrote:
> Hi Eryu,
>
> This series contains enhancements to overlay/017, which I used to test
> my work on overlayfs constant inode numbers. [1]
>
> The original test was a bit naiive, not taking into account renames,
> drop caches and mount cycle. All those are added by this series.
Thanks for the tests! Though usually we don't add new tests to existing
test cases, given that overlay/017 never passed before and won't pass
after adding these tests too, I think it's fine to merge this patchset,
as overlay/017 won't cause any false regression in tests.
Some minor comments go to individual patches.
Thanks,
Eryu
>
> My work covers only the inode numbers returned from stat(2) and not
> the inode numbers returned in d_ino from readdir(3), so the 'find -inum'
> part of this test could still fail with my overlayfs patches.
>
> However, I ran my tests in kvm-xfstests VM, where 'find -inum' called
> stat(2) for each entry, so the test did pass.
>
> I will dig deeper into this behavior when I work on fixing d_ino
> values in the next part of my work.
>
> Amir.
>
> [1] https://marc.info/?l=linux-unionfs&m=149324252301397&w=2
>
> Amir Goldstein (5):
> overlay/017: silence test output
> overlay/017: use af_unix to create socket test file
> overlay/017: create a helper to record inode number
> overlay/017: verify constant inode number after rename
> overlay/017: test persistent inode numbers after mount cycle
>
> tests/overlay/017 | 69 +++++++++++++++++++++++++++++++++++++++++++++------
> tests/overlay/017.out | 7 +-----
> 2 files changed, 62 insertions(+), 14 deletions(-)
>
> --
> 2.7.4
>
next prev parent reply other threads:[~2017-04-28 5:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 15:09 [PATCH 0/5] fstests: more tests for overlay constant inode numbers Amir Goldstein
2017-04-27 15:09 ` [PATCH 1/5] overlay/017: silence test output Amir Goldstein
2017-04-28 5:36 ` Eryu Guan
2017-04-28 5:45 ` Amir Goldstein
2017-04-28 5:50 ` Eryu Guan
2017-04-28 6:34 ` Amir Goldstein
2017-04-28 6:50 ` Eryu Guan
2017-04-27 15:09 ` [PATCH 2/5] overlay/017: use af_unix to create socket test file Amir Goldstein
2017-04-27 15:09 ` [PATCH 3/5] overlay/017: create a helper to record inode number Amir Goldstein
2017-04-27 15:09 ` [PATCH 4/5] overlay/017: verify constant inode number after rename Amir Goldstein
2017-04-28 5:47 ` Eryu Guan
2017-04-28 5:50 ` Amir Goldstein
2017-04-27 15:09 ` [PATCH 5/5] overlay/017: test persistent inode numbers after mount cycle Amir Goldstein
2017-04-28 5:30 ` Eryu Guan [this message]
2017-04-28 5:39 ` [PATCH 0/5] fstests: more tests for overlay constant inode numbers Amir Goldstein
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=20170428053020.GK26397@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=xzhou@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox