From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: test getbmap on reflinked files
Date: Sun, 3 Sep 2017 17:56:25 +0200 [thread overview]
Message-ID: <20170903155625.GA30509@lst.de> (raw)
In-Reply-To: <20170903155415.GH4073@magnolia>
On Sun, Sep 03, 2017 at 08:54:15AM -0700, Darrick J. Wong wrote:
> On Sun, Sep 03, 2017 at 02:14:51PM +0200, Christoph Hellwig wrote:
> > Test that we correctly report shared and unshared regions in a file.
> >
> > To do so we also update _filter_bmap to include the shared flag.
> >
> > Based on a test case from Darrick Wong.
>
> Which test case is that?
>
> Mostly I'm wondering how does this differ from xfs/280?
The one that you posted in reply to the getbmap patch.
It looks like that one is similar but doesn't look at the
detail shared vs unshared layout.
prev parent reply other threads:[~2017-09-03 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 12:14 test getbmap on reflinked files Christoph Hellwig
2017-09-03 15:54 ` Darrick J. Wong
2017-09-03 15:56 ` Christoph Hellwig [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=20170903155625.GA30509@lst.de \
--to=hch@lst.de \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@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