From: Christoph Hellwig <hch@lst.de>
To: fstests@vger.kernel.org
Cc: xfs@oss.sgi.com
Subject: [PATCH] generic/095: update warning whitelist
Date: Mon, 1 Aug 2016 11:02:56 +0200 [thread overview]
Message-ID: <1470042176-31447-1-git-send-email-hch@lst.de> (raw)
The recent direct I/O path refactor changed the function name in the
racing read case. Update the test case to handle the new name in
addition to the old one.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
tests/generic/095 | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/tests/generic/095 b/tests/generic/095
index c656ef1..4754992 100755
--- a/tests/generic/095
+++ b/tests/generic/095
@@ -125,9 +125,11 @@ $FIO_PROG $fio_config >>$seqres.full 2>&1
filter_xfs_dmesg()
{
local warn1="WARNING:.*fs/xfs/xfs_file\.c:.*xfs_file_dio_aio_write.*"
- local warn2="WARNING:.*fs/xfs/xfs_file\.c:.*xfs_file_read_iter.*"
+ 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.*"
sed -e "s#$warn1#Intentional warnings in xfs_file_dio_aio_write#" \
- -e "s#$warn2#Intentional warnings in xfs_file_read_iter#"
+ -e "s#$warn2#Intentional warnings in xfs_file_dio_aio_read#" \
+ -e "s#$warn3#Intentional warnings in xfs_file_read_iter#"
}
# umount before checking dmesg in case umount triggers any WARNING or Oops
--
2.1.4
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-08-01 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 9:02 Christoph Hellwig [this message]
2016-08-02 23:23 ` [PATCH] generic/095: update warning whitelist Dave Chinner
2016-08-03 7:39 ` Zorro Lang
2016-08-03 7:55 ` Eryu Guan
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=1470042176-31447-1-git-send-email-hch@lst.de \
--to=hch@lst.de \
--cc=fstests@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