* [PATCH] check: catch updated suspicious RCU usage message in _check_dmesg()
@ 2017-05-04 0:57 Eric Biggers
2017-05-04 5:09 ` Eryu Guan
0 siblings, 1 reply; 2+ messages in thread
From: Eric Biggers @ 2017-05-04 0:57 UTC (permalink / raw)
To: fstests; +Cc: Eric Biggers
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
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] check: catch updated suspicious RCU usage message in _check_dmesg()
2017-05-04 0:57 [PATCH] check: catch updated suspicious RCU usage message in _check_dmesg() Eric Biggers
@ 2017-05-04 5:09 ` Eryu Guan
0 siblings, 0 replies; 2+ messages in thread
From: Eryu Guan @ 2017-05-04 5:09 UTC (permalink / raw)
To: Eric Biggers; +Cc: fstests, Eric Biggers
On Wed, May 03, 2017 at 05:57:30PM -0700, Eric Biggers wrote:
> 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>
Thanks! I updated the commit log a bit to refer to kernel commit
4d4f88fa235f ("lockdep: Make RCU suspicious-access splats use pr_err")
Thanks,
Eryu
> ---
> 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
>
> --
> To unsubscribe from this list: send the line "unsubscribe fstests" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-05-04 5:09 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-05-04 0:57 [PATCH] check: catch updated suspicious RCU usage message in _check_dmesg() Eric Biggers
2017-05-04 5:09 ` Eryu Guan
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.