From: Dave Chinner <david@fromorbit.com>
To: Steve French <smfrench@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Josef Bacik <josef@toxicpanda.com>
Subject: Re: cross mount reflink and xfstest generic/373
Date: Wed, 6 Apr 2022 14:44:47 +1000 [thread overview]
Message-ID: <20220406044447.GD1609613@dread.disaster.area> (raw)
In-Reply-To: <CAH2r5muFq-4J=uedVF9qdYmFzgDDPwuYD+zrLytjUJE+APcBow@mail.gmail.com>
On Tue, Apr 05, 2022 at 11:48:29AM -0500, Steve French wrote:
> I like the patch which allows cross mount reflink (since in some cases
> like SMB3 mounts, cross mount reflink can now work depending on the
> volumes exported by the server) but was wondering if that means test
> generic/373 is getting any changes. In our test setup the btrfs
> directories we export over SMB3.1.1 for SCRATCH and TEST were on the
> partition on the server so reflink now works where test 373 expected
> them to fail. I can change our test setup to make sure SCRATCH and
> TEST are different volumes or server but was wondering if any recent
> changes to reflink related xfstests
>
> commit 9f5710bbfd3031dd7ce244fa26fba896d35f5342
> Author: Josef Bacik <josef@toxicpanda.com>
> Date: Fri Feb 18 09:38:14 2022 -0500
>
> fs: allow cross-vfsmount reflink/dedupe
https://lore.kernel.org/fstests/cover.1648153387.git.josef@toxicpanda.com/
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2022-04-06 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 16:48 cross mount reflink and xfstest generic/373 Steve French
2022-04-06 4:44 ` Dave Chinner [this message]
2022-04-08 2:01 ` Steve French
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=20220406044447.GD1609613@dread.disaster.area \
--to=david@fromorbit.com \
--cc=josef@toxicpanda.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=smfrench@gmail.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 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.