From: Eric Biggers <ebiggers@kernel.org> To: fstests@vger.kernel.org Cc: linux-fscrypt@vger.kernel.org, linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, Jaegeuk Kim <jaegeuk@kernel.org>, "Theodore Y . Ts'o" <tytso@mit.edu>, Victor Hsieh <victorhsieh@google.com> Subject: [RFC PATCH v2 1/8] common/filter: add _filter_xfs_io_fiemap() Date: Thu, 20 Jun 2019 14:36:07 -0700 [thread overview] Message-ID: <20190620213614.113685-2-ebiggers@kernel.org> (raw) In-Reply-To: <20190620213614.113685-1-ebiggers@kernel.org> From: Eric Biggers <ebiggers@google.com> Add _filter_xfs_io_fiemap() to clean up the output of 'xfs_io -c fiemap'. This will be used by a function in common/verity. Signed-off-by: Eric Biggers <ebiggers@google.com> --- common/filter | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/common/filter b/common/filter index ed082d24..9ad43ff4 100644 --- a/common/filter +++ b/common/filter @@ -541,6 +541,30 @@ _filter_filefrag() $flags, "\n"' } +# Clean up the extents list output of 'xfs_io -c fiemap', e.g. +# +# file: +# 0: [0..79]: 628365312..628365391 +# 1: [80..159]: hole +# 2: [160..319]: 628365472..628365631 +# => +# 0 79 628365312 628365391 +# 160 319 628365472 628365631 +# +# The fields are: +# +# first_logical_block last_logical_block first_physical_block last_physical_block +# +# Blocks are 512 bytes, and holes are omitted. +# +_filter_xfs_io_fiemap() +{ + grep -E '^[[:space:]]+[0-9]+:' \ + | grep -v '\<hole\>' \ + | sed -E 's/^[[:space:]]+[0-9]+://' \ + | tr '][.:' ' ' +} + # We generate WARNINGs on purpose when applications mix buffered/mmap IO with # direct IO on the same file. This is a helper for _check_dmesg() to filter out # such warnings. -- 2.22.0.410.gd8fdbe21b5-goog
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org> To: fstests@vger.kernel.org Cc: "Theodore Y . Ts'o" <tytso@mit.edu>, linux-f2fs-devel@lists.sourceforge.net, linux-fscrypt@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>, linux-ext4@vger.kernel.org, Victor Hsieh <victorhsieh@google.com> Subject: [f2fs-dev] [RFC PATCH v2 1/8] common/filter: add _filter_xfs_io_fiemap() Date: Thu, 20 Jun 2019 14:36:07 -0700 [thread overview] Message-ID: <20190620213614.113685-2-ebiggers@kernel.org> (raw) In-Reply-To: <20190620213614.113685-1-ebiggers@kernel.org> From: Eric Biggers <ebiggers@google.com> Add _filter_xfs_io_fiemap() to clean up the output of 'xfs_io -c fiemap'. This will be used by a function in common/verity. Signed-off-by: Eric Biggers <ebiggers@google.com> --- common/filter | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/common/filter b/common/filter index ed082d24..9ad43ff4 100644 --- a/common/filter +++ b/common/filter @@ -541,6 +541,30 @@ _filter_filefrag() $flags, "\n"' } +# Clean up the extents list output of 'xfs_io -c fiemap', e.g. +# +# file: +# 0: [0..79]: 628365312..628365391 +# 1: [80..159]: hole +# 2: [160..319]: 628365472..628365631 +# => +# 0 79 628365312 628365391 +# 160 319 628365472 628365631 +# +# The fields are: +# +# first_logical_block last_logical_block first_physical_block last_physical_block +# +# Blocks are 512 bytes, and holes are omitted. +# +_filter_xfs_io_fiemap() +{ + grep -E '^[[:space:]]+[0-9]+:' \ + | grep -v '\<hole\>' \ + | sed -E 's/^[[:space:]]+[0-9]+://' \ + | tr '][.:' ' ' +} + # We generate WARNINGs on purpose when applications mix buffered/mmap IO with # direct IO on the same file. This is a helper for _check_dmesg() to filter out # such warnings. -- 2.22.0.410.gd8fdbe21b5-goog _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2019-06-20 21:36 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-20 21:36 [RFC PATCH v2 0/8] xfstests: add fs-verity tests Eric Biggers 2019-06-20 21:36 ` [f2fs-dev] " Eric Biggers 2019-06-20 21:36 ` Eric Biggers [this message] 2019-06-20 21:36 ` [f2fs-dev] [RFC PATCH v2 1/8] common/filter: add _filter_xfs_io_fiemap() Eric Biggers 2019-06-20 21:36 ` [RFC PATCH v2 2/8] common/verity: add common functions for testing fs-verity Eric Biggers 2019-06-20 21:36 ` [f2fs-dev] " Eric Biggers 2019-06-20 21:36 ` [RFC PATCH v2 3/8] generic: test general behavior of verity files Eric Biggers 2019-06-20 21:36 ` [f2fs-dev] " Eric Biggers 2019-06-20 21:36 ` [RFC PATCH v2 4/8] generic: test access controls on the fs-verity ioctls Eric Biggers 2019-06-20 21:36 ` [f2fs-dev] " Eric Biggers 2019-06-20 21:36 ` [RFC PATCH v2 5/8] generic: test corrupting verity files Eric Biggers 2019-06-20 21:36 ` [f2fs-dev] " Eric Biggers 2019-06-20 21:36 ` [RFC PATCH v2 6/8] generic: test that fs-verity is using the correct measurement values Eric Biggers 2019-06-20 21:36 ` [f2fs-dev] " Eric Biggers 2019-06-20 21:36 ` [RFC PATCH v2 7/8] generic: test using fs-verity and fscrypt simultaneously Eric Biggers 2019-06-20 21:36 ` [f2fs-dev] " Eric Biggers 2019-06-20 21:36 ` [RFC PATCH v2 8/8] generic: test the fs-verity built-in signature verification support Eric Biggers 2019-06-20 21:36 ` [f2fs-dev] " Eric Biggers
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=20190620213614.113685-2-ebiggers@kernel.org \ --to=ebiggers@kernel.org \ --cc=fstests@vger.kernel.org \ --cc=jaegeuk@kernel.org \ --cc=linux-ext4@vger.kernel.org \ --cc=linux-f2fs-devel@lists.sourceforge.net \ --cc=linux-fscrypt@vger.kernel.org \ --cc=tytso@mit.edu \ --cc=victorhsieh@google.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: linkBe 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.