From: Dave Chinner <david@fromorbit.com>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 2/3] fstests: generic/374: validate cross-vfsmount dedupe
Date: Fri, 25 Mar 2022 11:08:16 +1100 [thread overview]
Message-ID: <20220325000816.GL1609613@dread.disaster.area> (raw)
In-Reply-To: <bad40a464e1728309e185a031e8d3652c22b68cf.1648153387.git.josef@toxicpanda.com>
On Thu, Mar 24, 2022 at 04:24:33PM -0400, Josef Bacik wrote:
> We allow for cross-vfsmount dedupes now, change this test to validate dedupe
> works properly cross-vfsmount.
>
> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
LGTM.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2022-03-25 0:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 20:24 [PATCH 0/3] fstests: cross-vfsmount reflink changes Josef Bacik
2022-03-24 20:24 ` [PATCH 1/3] fstests: generic/373: change test to validate cross-vfsmount reflink Josef Bacik
2022-03-25 0:07 ` Dave Chinner
2022-03-24 20:24 ` [PATCH 2/3] fstests: generic/374: validate cross-vfsmount dedupe Josef Bacik
2022-03-25 0:08 ` Dave Chinner [this message]
2022-03-24 20:24 ` [PATCH 3/3] fstests: btrfs/029: change the cross vfsmount reflink test Josef Bacik
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=20220325000816.GL1609613@dread.disaster.area \
--to=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).