From: Alex Elder <aelder@sgi.com>
To: Allison Henderson <achender@linux.vnet.ibm.com>
Cc: <linux-ext4@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<xfs@oss.sgi.com>
Subject: Re: [PATCH 4/4 v3] XFS TESTS: Fix 252 Failure: Add Generic FS Punch Hole Test 255
Date: Thu, 14 Jul 2011 09:37:48 -0500 [thread overview]
Message-ID: <1310654268.2067.5.camel@doink> (raw)
In-Reply-To: <4E1E1E41.30106@linux.vnet.ibm.com>
On Wed, 2011-07-13 at 15:37 -0700, Allison Henderson wrote:
> On 07/13/2011 09:31 AM, Alex Elder wrote:
> > On Wed, 2011-06-29 at 22:24 -0700, Allison Henderson wrote:
> >> This patch adds a new test 255 that tests fallocate punch hole,
> >> but is for use by generic filesystems. It is similar to 252,
> >> but uses a weaker fiemap filter that only displays the location
> >> of the hole, and not the extent types.
> >>
> >> Signed-off-by: Allison Henderson<achender@linux.vnet.ibm.com>
> >
> > I realize Christoph already committed this but I
> > spotted something so I thought I might as well
> > mention it. I haven't tested any of this, so
> > it may be OK after all, but if it's not then
> > the filter_hole_fiemap() function ought to be
> > updated.
> >
> > -Alex
> >
> > . . .
> >
> >> diff --git a/common.punch b/common.punch
> >> index c18f88a..a48b7ae 100644
> >> --- a/common.punch
> >> +++ b/common.punch
> >> @@ -218,6 +218,23 @@ _filter_fiemap()
> >> _coalesce_extents
> >> }
> >>
> >> +# Filters fiemap output to only print the
> >> +# file offset column and whether or not
> >> +# it is an extent or a hole
> >> +_filter_hole_fiemap()
> >> +{
> >> + awk --posix '
> >> + $3 ~ /hole/ {
> >> + print $1, $2, $3;
> >> + next;
> >> + }
> >> + $5 ~ /0x[[:digit:]]+/ {
> >
> > I believe this should be:
> > $5 ~ /0x[[:xdigit:]]+/ {
> >
> > (I.e., hex digits, not just decimals.)
> >
>
> Hi Alex,
>
> I think you are right. The extent flags are printed in hex, so it
> should be xdigit. The existing _filter_fiemap routine that I modeled
> this code from is also only parsing decimal digits. Even though the
> tests are not showing any problems right now, it should probably be
> fixed. Should I submit a patch to correct it?
Please, yes--to fix both. And please verify the problem
while you're at it if possible. Thank you.
-Alex
> Allison Henderson
>
> >> + print $1, $2, "extent";
> >> + }' |
> >> + _coalesce_extents
> >> +}
> >> +
> >> +
> >> # Prints the md5 checksum of a given file
> >> _md5_checksum()
> >> {
> >
> > . . .
> >
>
next prev parent reply other threads:[~2011-07-14 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 5:23 [PATCH 0/4 v3] XFS TESTS: Fix 252 failure Allison Henderson
2011-06-30 5:23 ` [PATCH 1/4 v3] XFS TESTS: Fix 252 Failure: Make 252 xfs only with MD5 checksum Allison Henderson
2011-06-30 5:23 ` [PATCH 2/4 v3] XFS TESTS: Fix 252 Failure: Update 252 Golden Output Allison Henderson
2011-06-30 5:24 ` [PATCH 3/4 v3] XFS TESTS: Fix 252 Failure: Update 242 " Allison Henderson
2011-06-30 5:24 ` [PATCH 4/4 v3] XFS TESTS: Fix 252 Failure: Add Generic FS Punch Hole Test 255 Allison Henderson
2011-07-13 16:31 ` Alex Elder
2011-07-13 22:37 ` Allison Henderson
2011-07-14 14:37 ` Alex Elder [this message]
2011-07-13 12:38 ` [PATCH 0/4 v3] XFS TESTS: Fix 252 failure Christoph Hellwig
2011-07-13 22:25 ` Allison Henderson
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=1310654268.2067.5.camel@doink \
--to=aelder@sgi.com \
--cc=achender@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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).