public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: fstests@vger.kernel.org
Subject: [PATCH] generic/095: add iomap_dio_rw() to the dmesg filter
Date: Wed, 30 Nov 2016 15:59:08 +1100	[thread overview]
Message-ID: <20161130045908.15200-1-david@fromorbit.com> (raw)

From: Dave Chinner <dchinner@redhat.com>

Oops, we did it again - we moved the XFS dio code warning to a new
function with the iomap direct IO rework.  Update the filter to pick
up the new warning location.

Signed-Off-By: Dave Chinner <dchinner@redhat.com>
---
 tests/generic/095 | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/tests/generic/095 b/tests/generic/095
index 474825bdf8d6..991baefaecdf 100755
--- a/tests/generic/095
+++ b/tests/generic/095
@@ -128,10 +128,12 @@ filter_xfs_dmesg()
 	local warn2="WARNING:.*fs/xfs/xfs_file\.c:.*xfs_file_dio_aio_read.*"
 	local warn3="WARNING:.*fs/xfs/xfs_file\.c:.*xfs_file_read_iter.*"
 	local warn4="WARNING:.*fs/xfs/xfs_file\.c:.*xfs_file_aio_read.*"
+	local warn4="WARNING:.*fs/iomap\.c:.*iomap_dio_rw.*"
 	sed -e "s#$warn1#Intentional warnings in xfs_file_dio_aio_write#" \
 	    -e "s#$warn2#Intentional warnings in xfs_file_dio_aio_read#" \
 	    -e "s#$warn3#Intentional warnings in xfs_file_read_iter#" \
-	    -e "s#$warn4#Intentional warnings in xfs_file_aio_read#"
+	    -e "s#$warn4#Intentional warnings in xfs_file_aio_read#" \
+	    -e "s#$warn4#Intentional warnings in iomap_dio_rw#"
 }
 
 # umount before checking dmesg in case umount triggers any WARNING or Oops
-- 
2.10.2


             reply	other threads:[~2016-11-30  4:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30  4:59 Dave Chinner [this message]
2016-11-30 16:13 ` [PATCH] generic/095: add iomap_dio_rw() to the dmesg filter Christoph Hellwig

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=20161130045908.15200-1-david@fromorbit.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox