From: Eryu Guan <eguan@redhat.com>
To: Lu Fengqi <lufq.fnst@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org, fdmanana@gmail.com
Subject: Re: [PATCH v4] fstests: btrfs: add test for qgroup handle extent de-reference
Date: Tue, 14 Jun 2016 18:22:23 +0800 [thread overview]
Message-ID: <20160614102223.GR5140@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1465868559-10997-1-git-send-email-lufq.fnst@cn.fujitsu.com>
On Tue, Jun 14, 2016 at 09:42:39AM +0800, Lu Fengqi wrote:
> Test if qgroup can handle extent de-reference during reallocation.
> "extent de-reference" means that reducing an extent's reference count
> or freeing an extent.
> Although current qgroup can handle it, we still need to prevent any
> regression which may break current qgroup.
>
> Signed-off-by: Lu Fengqi <lufq.fnst@cn.fujitsu.com>
Looks good to me.
Reviewed-by: Eryu Guan <eguan@redhat.com>
prev parent reply other threads:[~2016-06-14 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 1:42 [PATCH v4] fstests: btrfs: add test for qgroup handle extent de-reference Lu Fengqi
2016-06-14 10:22 ` 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=20160614102223.GR5140@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=fdmanana@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lufq.fnst@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).