public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH 6/7] xfs: test rmap behavior when multiple bmbt records map to a single rmapbt record
Date: Thu, 26 May 2016 01:04:24 -0700	[thread overview]
Message-ID: <20160526080424.GA8469@infradead.org> (raw)
In-Reply-To: <146424226290.6278.15051221437554845000.stgit@birch.djwong.org>

> --- a/src/t_immutable.c
> +++ b/src/t_immutable.c
> @@ -38,10 +38,10 @@
>  #include <libgen.h>
>  #include <sys/acl.h>
>  #include <attr/xattr.h>
> +#include <linux/fs.h>
>  #include <xfs/xfs.h>
>  #include <xfs/handle.h>
>  #include <xfs/jdm.h>
> -#include <linux/fs.h>
>  #include <linux/magic.h>
>  
>  #ifndef XFS_SUPER_MAGIC

How does this belong into the patch?

> diff --git a/tests/xfs/group b/tests/xfs/group
> index f0ca410..0e34f9a 100644
> --- a/tests/xfs/group
> +++ b/tests/xfs/group
> @@ -288,3 +288,4 @@
>  853 auto quick clone
>  854 auto quick clone
>  855 auto clone
> +856 auto clone rmap reflink

This is the only test in the reflink group, how is this group different
from the clone one?

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2016-05-26  8:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-26  5:57 [PATCH 0/7] xfstests: minor fixes for the reflink/dedupe tests Darrick J. Wong
2016-05-26  5:57 ` [PATCH 1/7] xfs/104: don't enospc when ag metadata overhead grows Darrick J. Wong
2016-05-26  8:08   ` Christoph Hellwig
2016-05-26  5:57 ` [PATCH 2/7] tests: don't put loop control files on the scratch mount Darrick J. Wong
2016-05-26  8:09   ` Christoph Hellwig
2016-05-26 16:07     ` Darrick J. Wong
2016-05-27  3:28   ` [PATCH v2 " Darrick J. Wong
2016-05-31 12:52     ` Christoph Hellwig
2016-05-26  5:57 ` [PATCH 3/7] xfs: test copy-on-write leftover recovery Darrick J. Wong
2016-05-26  8:22   ` Christoph Hellwig
2016-05-26  5:57 ` [PATCH 4/7] xfs: test per-ag allocation accounting during truncate-caused refcountbt expansion Darrick J. Wong
2016-05-26  8:23   ` Christoph Hellwig
2016-05-26  5:57 ` [PATCH 5/7] reflink: test interaction with swap files Darrick J. Wong
2016-05-26  8:24   ` Christoph Hellwig
2016-05-26  5:57 ` [PATCH 6/7] xfs: test rmap behavior when multiple bmbt records map to a single rmapbt record Darrick J. Wong
2016-05-26  8:04   ` Christoph Hellwig [this message]
2016-05-26 16:12     ` Darrick J. Wong
2016-05-27  3:28   ` [PATCH v2 " Darrick J. Wong
2016-05-31 12:52     ` Christoph Hellwig
2016-05-26  5:57 ` [PATCH 7/7] reflink: test changing sharers of a block while keeping refcount the same Darrick J. Wong
2016-05-26  8:24   ` Christoph Hellwig
2016-05-26  7:31 ` question about xfs/122 Xiao Yang
2016-05-26 16:32   ` Darrick J. Wong
2016-05-27 18:02 ` [PATCH 8/7] xfs/122: don't break on old xfsprogs Darrick J. Wong
2016-05-31 12:51   ` Christoph Hellwig
2016-05-31 16:41     ` Darrick J. Wong
2016-05-31 16:43   ` [PATCH v2 " Darrick J. Wong
2016-05-31 19:33     ` Christoph Hellwig

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=20160526080424.GA8469@infradead.org \
    --to=hch@infradead.org \
    --cc=darrick.wong@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=xfs@oss.sgi.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