From: Dave Chinner <david@fromorbit.com>
To: fstests@vger.kernel.org
Subject: Re: [PATCH] filter: xfs_io output has dropped "64" from error messages
Date: Thu, 3 Nov 2016 08:07:18 +1100 [thread overview]
Message-ID: <20161102210718.GF14023@dastard> (raw)
In-Reply-To: <1478060636-25272-1-git-send-email-david@fromorbit.com>
On Wed, Nov 02, 2016 at 03:23:56PM +1100, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> Upstream xfs_io has been converted to always use LFS compliant
> (i.e. 64 bit) pwrite() rather than pwrite64(). Similar changes have
> been made for multiple syscalls that have "*64" variants. hence the
> error output of all these commands has changed, such as "pwrite64:
> ..." to "pwrite: ....".
>
> Make a filter to catch the *64 variants and strip it, and
> convert all the golden output to use the non-*64 variant. This will
> make all golden output matching work correctly regardless of what
> version of xfs_io is in use.
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
....
Actually, overnight testing found a bug in this patch:
> --- a/tests/f2fs/001
> +++ b/tests/f2fs/001
> @@ -69,10 +69,8 @@ $XFS_IO_PROG -t -f -c "falloc 0 5g" $dummyfile | _filter_xfs_io
>
> # -ENOSPC should be triggered without any panic
> echo "==== change i_size & write data ===="
> -$XFS_IO_PROG \
> - -c "truncate 96" \
> - -c "pwrite -S 0x58 8192 4096" \
> -$testfile | _filter_xfs_io
> +$XFS_IO_PROG -c "truncate 96" -c "pwrite -S 0x58 8192 4096" $testfile \
> + | _filter_xfs_io_error
This is missing a 2>&1 redirection, so the filter won't work. I'll
post and updated patch in a minute.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-11-02 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 4:23 [PATCH] filter: xfs_io output has dropped "64" from error messages Dave Chinner
2016-11-02 17:29 ` Darrick J. Wong
2016-11-02 21:07 ` Dave Chinner [this message]
2016-11-02 21:15 ` [PATCH V2] " Dave Chinner
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=20161102210718.GF14023@dastard \
--to=david@fromorbit.com \
--cc=fstests@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.