From: Eryu Guan <guan@eryu.me>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Eryu Guan <guaneryu@gmail.com>,
Chengguang Xu <cgxu519@mykernel.net>,
Miklos Szeredi <miklos@szeredi.hu>,
overlayfs <linux-unionfs@vger.kernel.org>,
fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH v5] overlay: test for whiteout inode sharing
Date: Mon, 18 May 2020 00:47:44 +0800 [thread overview]
Message-ID: <20200517164744.GH2704@desktop> (raw)
In-Reply-To: <CAOQ4uxhtOSsi41z_kCA2ihCKVEg3FTxg892OHgCB22j60LQHoA@mail.gmail.com>
On Sun, May 17, 2020 at 07:42:32PM +0300, Amir Goldstein wrote:
> On Sun, May 17, 2020 at 7:24 PM Eryu Guan <guan@eryu.me> wrote:
> >
> > On Wed, May 13, 2020 at 10:23:38PM +0300, Amir Goldstein wrote:
> > > From: Chengguang Xu <cgxu519@mykernel.net>
> > >
> > > This is a test for whiteout inode sharing feature.
> > >
> > > [Amir] added check for whiteout sharing support
> > > and whiteout of lower dir.
> > >
> > > Signed-off-by: Chengguang Xu <cgxu519@mykernel.net>
> > > Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> > > ---
> > >
> > > Chengguang,
> > >
> > > I decided to take a stab at Eryu's challenge ;-)
> >
> > Great! Thanks for the update!
> >
>
> FYI, not sure if and when that was mentioned.
> inode sharing feature is now on overlayfs-next.
>
> So are the two file handle fixes for which I posted the test:
> "overlay: regression test for two file handle bugs"
> (will re-post when I have the final kernel commits)
Thanks! I noticed this test would oops kernel, so I didn't take it this
time and will wait until the fix goes to mainline kernel.
Thanks,
Eryu
prev parent reply other threads:[~2020-05-17 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 19:23 [PATCH v5] overlay: test for whiteout inode sharing Amir Goldstein
2020-05-14 7:55 ` 回复:[PATCH " Chengguang Xu
2020-05-17 16:24 ` [PATCH " Eryu Guan
2020-05-17 16:42 ` Amir Goldstein
2020-05-17 16:47 ` Eryu Guan [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=20200517164744.GH2704@desktop \
--to=guan@eryu.me \
--cc=amir73il@gmail.com \
--cc=cgxu519@mykernel.net \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@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 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.