From: Eric Biggers <ebiggers3@gmail.com>
To: fstests@vger.kernel.org
Cc: Eric Biggers <ebiggers@google.com>
Subject: [PATCH] check: catch updated suspicious RCU usage message in _check_dmesg()
Date: Wed, 3 May 2017 17:57:30 -0700 [thread overview]
Message-ID: <20170504005730.29862-1-ebiggers3@gmail.com> (raw)
From: Eric Biggers <ebiggers@google.com>
In the v4.11 kernel, the suspicious RCU usage message uses the word
"ERR" rather than "INFO". Update _check_dmesg to accept both versions.
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
common/rc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/common/rc b/common/rc
index 8dafd4bc..257b1903 100644
--- a/common/rc
+++ b/common/rc
@@ -3285,13 +3285,13 @@ _check_dmesg()
# use sed \cregexpc address type, since $seqnum contains "/"
dmesg | tac | sed -ne "0,\#run fstests $seqnum at $date_time#p" | \
tac | $filter >$seqres.dmesg
- grep -q -e "kernel BUG at" \
+ egrep -q -e "kernel BUG at" \
-e "WARNING:" \
-e "BUG:" \
-e "Oops:" \
-e "possible recursive locking detected" \
-e "Internal error" \
- -e "INFO: suspicious RCU usage" \
+ -e "(INFO|ERR): suspicious RCU usage" \
-e "INFO: possible circular locking dependency detected" \
-e "general protection fault:" \
$seqres.dmesg
--
2.13.0.rc1.294.g07d810a77f-goog
next reply other threads:[~2017-05-04 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 0:57 Eric Biggers [this message]
2017-05-04 5:09 ` [PATCH] check: catch updated suspicious RCU usage message in _check_dmesg() 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=20170504005730.29862-1-ebiggers3@gmail.com \
--to=ebiggers3@gmail.com \
--cc=ebiggers@google.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