From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Eryu Guan <eguan@redhat.com>,
fstests@vger.kernel.org, Dave Chinner <david@fromorbit.com>
Cc: Jan Kara <jack@suse.cz>,
linux-nvdimm@lists.01.org, Christoph Hellwig <hch@lst.de>,
linux-ext4@vger.kernel.org
Subject: [fstests PATCH v2 0/2] Add test for DAX+ext4+DMA race
Date: Tue, 10 Jul 2018 16:09:40 -0600 [thread overview]
Message-ID: <20180710220942.21074-1-ross.zwisler@linux.intel.com> (raw)
As of kernel version 4.18-rc4, Linux has an issue with ext4+DAX where DMA
and direct I/O operations aren't synchronized with respect to operations
which can change the block mappings of an inode. This can potentially
lead to data corruption, and is fixed in the following kernel series:
https://lists.01.org/pipermail/linux-nvdimm/2018-July/016842.html
These patches add a regression test for that series.
---
Changes since v1:
* Added copyright and license information to files I've previously
authored in src/.
* Added copyright, license information and info about the test's
purpose to src/t_mmap_collision.c. (Dave)
* Added comments to tests/generic/999 explaining why we unset the
mount flags for SCRATCH_MNT. (Dave)
* Subtests in src/t_mmap_collision.c are now conditional based on the
existence of the necessary FALLOC_FL_* flags. (Eryu)
* Added the test to the punch, collapse and zero groups. (Eryu)
Ross Zwisler (2):
src/: add license and copyright info to files
generic/999: test DAX DMA vs truncate/hole-punch
.gitignore | 1 +
src/Makefile | 2 +-
src/t_ext4_dax_inline_corruption.c | 2 +
src/t_ext4_dax_journal_corruption.c | 2 +
src/t_mmap_collision.c | 235 ++++++++++++++++++++++++++++++++++++
src/t_mmap_cow_race.c | 2 +
src/t_mmap_stale_pmd.c | 2 +
tests/generic/999 | 53 ++++++++
tests/generic/999.out | 2 +
tests/generic/group | 1 +
10 files changed, 301 insertions(+), 1 deletion(-)
create mode 100644 src/t_mmap_collision.c
create mode 100755 tests/generic/999
create mode 100644 tests/generic/999.out
--
2.14.4
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next reply other threads:[~2018-07-10 22:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 22:09 Ross Zwisler [this message]
2018-07-10 22:09 ` [fstests PATCH v2 1/2] src/: add license and copyright info to files Ross Zwisler
2018-07-14 12:54 ` Eryu Guan
2018-07-10 22:09 ` [fstests PATCH v2 2/2] generic/999: test DAX DMA vs truncate/hole-punch Ross Zwisler
2018-07-14 1:41 ` Dave Chinner
2018-07-16 16:07 ` Ross Zwisler
2018-07-14 12:53 ` Eryu Guan
2018-07-27 21:12 ` [fstests PATCH v3] " Ross Zwisler
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=20180710220942.21074-1-ross.zwisler@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=david@fromorbit.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-nvdimm@lists.01.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).