From: Xiong Zhou <xzhou@redhat.com>
To: Eryu Guan <eguan@redhat.com>
Cc: Xiong Zhou <xzhou@redhat.com>, fstests@vger.kernel.org
Subject: Re: [PATCH v2] overlay: test memleak in copy-up error handling path
Date: Fri, 27 May 2016 13:46:09 +0800 [thread overview]
Message-ID: <20160527054609.GC2933@dhcp12-144.nay.redhat.com> (raw)
In-Reply-To: <20160526072426.GZ5140@eguan.usersys.redhat.com>
On Thu, May 26, 2016 at 03:24:26PM +0800, Eryu Guan wrote:
> On Tue, May 10, 2016 at 10:32:45AM +0800, Xiong Zhou wrote:
> > This memleak leads to panic when unmount the underlying fs.
> > Kernel commit ab79efab0 fixed this issue.
> >
> > Signed-off-by: Xiong Zhou <xzhou@redhat.com>
> > ---
> >
> > Diff to v1:
> > set up underlying fs in $SCRATCH_DEV instead of $SCRATCH_MNT
> > xfs_io open test_file instead of src/writemod
> > use little upper dir to trigger ENOSP failure instead of kill
> > clean up in cleanup
>
> Thanks for the update! And sorry for late review.. Some minor issues
> inline
Thank you very much for the tips! Sending v3.
--
Xiong
prev parent reply other threads:[~2016-05-27 5:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 12:23 [PATCH] overlay: test basic whiteout Xiong Zhou
2016-04-21 12:57 ` Eryu Guan
2016-04-21 13:15 ` Xiong Zhou
2016-04-22 8:11 ` [PATCH 1/2] " Xiong Zhou
2016-04-22 8:11 ` [PATCH 2/2] overlay: notrun if upper fs does not support d_type Xiong Zhou
2016-04-22 9:21 ` [PATCH v2] " Xiong Zhou
2016-04-22 10:24 ` Eryu Guan
2016-04-22 10:09 ` [PATCH 1/2] overlay: test basic whiteout Eryu Guan
2016-05-04 6:53 ` [PATCH] overlay: test copy up by changing mode bits Xiong Zhou
2016-05-04 9:26 ` Eryu Guan
2016-05-09 4:12 ` [PATCH] overlay: test memleak in copy up error handling path Xiong Zhou
2016-05-10 2:32 ` [PATCH v2] overlay: test memleak in copy-up " Xiong Zhou
2016-05-26 7:24 ` Eryu Guan
2016-05-27 5:46 ` Xiong Zhou [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=20160527054609.GC2933@dhcp12-144.nay.redhat.com \
--to=xzhou@redhat.com \
--cc=eguan@redhat.com \
--cc=fstests@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