From: Jan Kara <jack@suse.com>
To: fstests@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, Jan Kara <jack@suse.com>
Subject: [PATCH 2/4] ext4/001: Update output
Date: Wed, 4 Nov 2015 17:31:36 +0100 [thread overview]
Message-ID: <1446654698-23577-3-git-send-email-jack@suse.com> (raw)
In-Reply-To: <1446654698-23577-1-git-send-email-jack@suse.com>
After patch "ext4: Fix races of writeback with punch hole and zero
range" we don't flush range that's going to be zeroed out which results
in different final extent layout because some extents will be zeroed-out
instead of being split. Update the output file accordingly.
Signed-off-by: Jan Kara <jack@suse.com>
---
tests/ext4/001.out | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/tests/ext4/001.out b/tests/ext4/001.out
index 212c24783387..c2f728483b23 100644
--- a/tests/ext4/001.out
+++ b/tests/ext4/001.out
@@ -131,14 +131,10 @@ cc63069677939f69a6e8f68cae6a6dac
2: [32..39]: hole
daa100df6e6711906b61c9ab5aa16032
11. data -> hole -> data
-0: [0..7]: data
-1: [8..31]: unwritten
-2: [32..39]: data
+0: [0..39]: data
f6aeca13ec49e5b266cd1c913cd726e3
12. unwritten -> data -> unwritten
-0: [0..7]: data
-1: [8..31]: unwritten
-2: [32..39]: data
+0: [0..39]: unwritten
daa100df6e6711906b61c9ab5aa16032
13. data -> unwritten -> data
0: [0..7]: data
--
2.1.4
next prev parent reply other threads:[~2015-11-04 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 16:31 [PATCH 0/4] Output selection, improvements for ext4/001 Jan Kara
2015-11-04 16:31 ` [PATCH 1/4] _filter_fiemap: Avoid awk interval regexps Jan Kara
2015-11-04 16:31 ` Jan Kara [this message]
2015-11-04 16:31 ` [PATCH 3/4] common: Add function for selecting from different output files Jan Kara
2015-11-16 21:29 ` Dave Chinner
2015-11-18 15:37 ` Jan Kara
2015-11-04 16:31 ` [PATCH 4/4] ext4/001: Select different output based on mount options 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=1446654698-23577-3-git-send-email-jack@suse.com \
--to=jack@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@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).