linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: "Boylston, Brian" <brian.boylston@hpe.com>
Cc: Jan Kara <jack@suse.com>, Ted Tso <tytso@mit.edu>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	Ross Zwisler <ross.zwisler@linux.intel.com>,
	"dan.j.williams@intel.com" <dan.j.williams@intel.com>
Subject: Re: [PATCH 0/9 v3] ext4: Punch hole and DAX fixes
Date: Mon, 9 Nov 2015 17:22:56 +0100	[thread overview]
Message-ID: <20151109162256.GH11149@quack.suse.cz> (raw)
In-Reply-To: <80B02B5F638F054B8B1358323FECDE0A5EA64CCF@G1W3650.americas.hpqcorp.net>

  Hi,

On Fri 06-11-15 17:57:04, Boylston, Brian wrote:
> I've written a test tool (included below) that exercises page faults on
> hole-y portions of an mmapped file.  The file is created, sized using
> various methods, mmapped, and then two threads race to write a marker to
> different offsets within each mapped page.  Once the threads have
> finished marking each page, the pages are checked for the presence of
> the markers.
> 
> With vanilla 4.2 and 4.3 kernels, this test easily exposes corruption on
> pmem-backed, DAX-mounted xfs and ext4 file systems.
> 
> With 4.3 and this ext4 patch set, the data corruption is still seen:
> 
> $ ./holetest -f /pmem1/brian/holetest 1000
> holetest r207

Thanks for the test. I'll try to reproduce locally and have a look why
my block zeroing patch didn't work as expected.

								Honza
> 
> INFO: zero-filled test...
> INFO: sz = 3e800000, npages = 256000
> INFO: vastart = 00007f2ad0bd0000
> INFO: thread 0 is 7f2ad0bcf700
> INFO: thread 1 is 7f2ad03ce700
> INFO: 0 error(s) detected
> 
> INFO: posix_fallocate test...
> INFO: sz = 3e800000, npages = 256000
> INFO: vastart = 00007f2ad0bd0000
> INFO: thread 0 is 7f2ad03ce700
> INFO: thread 1 is 7f2ad0bcf700
> INFO: 0 error(s) detected
> 
> INFO: fallocate test...
> INFO: sz = 3e800000, npages = 256000
> INFO: vastart = 00007f2ad0bd0000
> INFO: thread 0 is 7f2ad0bcf700
> INFO: thread 1 is 7f2ad03ce700
> INFO: 0 error(s) detected
> 
> INFO: ftruncate test...
> INFO: sz = 3e800000, npages = 256000
> INFO: vastart = 00007f2ad0bd0000
> INFO: thread 0 is 7f2ad03ce700
> INFO: thread 1 is 7f2ad0bcf700
> ERROR: thread 0, offset 01001c00, 00000000 != 7f2ad03ce700
> ERROR: thread 0, offset 01801c00, 00000000 != 7f2ad03ce700
> ERROR: thread 0, offset 02001c00, 00000000 != 7f2ad03ce700
> ERROR: thread 0, offset 02807c00, 00000000 != 7f2ad03ce700
> ERROR: thread 0, offset 0281dc00, 00000000 != 7f2ad03ce700
> ERROR: thread 0, offset 03001c00, 00000000 != 7f2ad03ce700
> ERROR: thread 0, offset 03023c00, 00000000 != 7f2ad03ce700
> ERROR: thread 0, offset 03801c00, 00000000 != 7f2ad03ce700
> ERROR: thread 0, offset 03804c00, 00000000 != 7f2ad03ce700
> ERROR: thread 0, offset 04001c00, 00000000 != 7f2ad03ce700
> ERROR: thread 0, offset 04801c00, 00000000 != 7f2ad03ce700
> ERROR: thread 0, offset 05001c00, 00000000 != 7f2ad03ce700
> ERROR: thread 1, offset 0e001400, 00000000 != 7f2ad0bcf700
> ERROR: thread 1, offset 16001400, 00000000 != 7f2ad0bcf700
> ERROR: thread 1, offset 1b001400, 00000000 != 7f2ad0bcf700
> ERROR: thread 1, offset 2a802400, 00000000 != 7f2ad0bcf700
> ERROR: thread 1, offset 31005400, 00000000 != 7f2ad0bcf700
> ERROR: thread 0, offset 3e6b3c00, 00000000 != 7f2ad03ce700
> INFO: 18 error(s) detected
> $
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

  parent reply	other threads:[~2015-11-09 16:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 16:18 [PATCH 0/9 v3] ext4: Punch hole and DAX fixes Jan Kara
2015-11-04 16:18 ` [PATCH 1/9] ext4: Fix races between page faults and hole punching Jan Kara
2015-11-04 16:18 ` [PATCH 2/9] ext4: Move unlocked dio protection from ext4_alloc_file_blocks() Jan Kara
2015-11-04 16:18 ` [PATCH 3/9] ext4: Fix races between buffered IO and collapse / insert range Jan Kara
2015-11-04 16:18 ` [PATCH 4/9] ext4: Fix races of writeback with punch hole and zero range Jan Kara
2015-11-04 16:18 ` [PATCH 5/9] ext4: Document lock ordering Jan Kara
2015-11-04 16:18 ` [PATCH 6/9] ext4: Get rid of EXT4_GET_BLOCKS_NO_LOCK flag Jan Kara
2015-11-04 16:18 ` [PATCH 7/9] ext4: Provide ext4_issue_zeroout() Jan Kara
2015-11-04 16:18 ` [PATCH 8/9] ext4: Implement allocation of pre-zeroed blocks Jan Kara
2015-11-04 16:18 ` [PATCH 9/9] ext4: Use pre-zeroed blocks for DAX page faults Jan Kara
2015-11-04 18:51 ` [PATCH 0/9 v3] ext4: Punch hole and DAX fixes Ross Zwisler
2015-11-06 17:57 ` Boylston, Brian
2015-11-06 22:17   ` Dave Chinner
2015-11-09 16:22   ` Jan Kara [this message]
2015-11-09 16:51     ` Jan Kara
2015-11-10  0:00       ` Dave Chinner
2015-11-10 10:02         ` Jan Kara
2015-11-10 22:31           ` Dave Chinner
2015-11-11 15:25             ` Jan Kara

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=20151109162256.GH11149@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=brian.boylston@hpe.com \
    --cc=dan.j.williams@intel.com \
    --cc=jack@suse.com \
    --cc=linux-ext4@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).