From: xuyang <xuyang2018.jy@cn.fujitsu.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: guaneryu@gmail.com, linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 0/3] fstests: various fixes
Date: Thu, 9 May 2019 10:21:12 +0800 [thread overview]
Message-ID: <5CD38E98.8000705@cn.fujitsu.com> (raw)
In-Reply-To: <155724821034.2624631.4172554705843296757.stgit@magnolia>
on 2019/05/08 0:56, Darrick J. Wong wrote:
> Hi all,
>
> Here are three patches fixing various regressions in xfstests when
> mkfs.xfs defaults to enabling reflink and/or rmap by default. Most of
> the changes deal with the change in minimum log size requirements. They
> weren't caught until now because there are a number of tests that call
> mkfs on a loop device or a file without using MKFS_OPTIONS.
>
> If you're going to start using this mess, you probably ought to just
> pull from my git trees, which are linked below.
>
> This is an extraordinary way to destroy everything. Enjoy!
> Comments and questions are, as always, welcome.
>
> --D
>
> fstests git tree:
> https://git.kernel.org/cgit/linux/kernel/git/djwong/xfstests-dev.git/log/?h=random-fixes
>
>
>
Hi
Tested-by: Yang Xu<xuyang2018.jy@cn.fujitsu.com>
next prev parent reply other threads:[~2019-05-09 2:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 16:56 [PATCH 0/3] fstests: various fixes Darrick J. Wong
2019-05-07 16:56 ` [PATCH 1/3] xfs: refactor minimum log size formatting code Darrick J. Wong
2019-05-07 16:57 ` [PATCH 2/3] xfs/216: always disable rmap and reflink when creating log size test fs Darrick J. Wong
2019-05-07 16:57 ` [PATCH 3/3] xfs/294: calculate space to reserve for fragmentation test Darrick J. Wong
2019-05-09 2:21 ` xuyang [this message]
2019-05-10 8:47 ` [PATCH 0/3] fstests: various fixes Eryu Guan
2019-05-10 8:52 ` xuyang
-- strict thread matches above, loose matches on Subject: below --
2019-05-20 22:30 Darrick J. Wong
2019-06-04 21:16 Darrick J. Wong
2019-07-09 17:49 Darrick J. Wong
2019-07-24 4:12 Darrick J. Wong
2019-08-15 15:18 Darrick J. Wong
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=5CD38E98.8000705@cn.fujitsu.com \
--to=xuyang2018.jy@cn.fujitsu.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).