From: Eryu Guan <eguan@redhat.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: fstests@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Theodore Ts'o <tytso@mit.edu>, Christoph Hellwig <hch@lst.de>,
Dan Williams <dan.j.williams@intel.com>,
Dave Chinner <david@fromorbit.com>, Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org, linux-nvdimm@lists.01.org,
linux-xfs@vger.kernel.org, Andreas Dilger <adilger@dilger.ca>
Subject: Re: [PATCH 3/3] ext4: test for inline data + DAX corruption
Date: Wed, 13 Sep 2017 15:16:35 +0800 [thread overview]
Message-ID: <20170913071635.GB8034@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170912044521.22644-3-ross.zwisler@linux.intel.com>
On Mon, Sep 11, 2017 at 10:45:21PM -0600, Ross Zwisler wrote:
> Add a regression test for the following kernel commit:
>
> ext4: prevent data corruption with inline data + DAX
>
> The test passes either if we don't encounter corruption, or if mounting
> with DAX + inline data fails. The latter is the way that we prevent this
> issue in the kernel.
>
> Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
Besides the gitignore entry order issue and call the test program from
$here/src/... issue, need another require rule:
_require_ext4_mkfs_feature "inline_data"
Otherwise this looks fine to me.
Thanks,
Eryu
prev parent reply other threads:[~2017-09-13 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 4:45 [PATCH 1/3] .gitignore: ignore cscope files Ross Zwisler
[not found] ` <20170912044521.22644-1-ross.zwisler-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-09-12 4:45 ` [PATCH 2/3] ext4: test for DAX + journaling corruption Ross Zwisler
[not found] ` <20170912044521.22644-2-ross.zwisler-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-09-13 7:06 ` Eryu Guan
2017-09-12 4:45 ` [PATCH 3/3] ext4: test for inline data + DAX corruption Ross Zwisler
2017-09-13 7:16 ` Eryu Guan [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=20170913071635.GB8034@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=adilger@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ross.zwisler@linux.intel.com \
--cc=tytso@mit.edu \
/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).