path: root/tools/testing/selftests/rcutorture/bin/parse-console.sh
diff options
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>2014-08-26 11:35:43 -0700
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>2014-09-07 16:24:49 -0700
commitbc51896da2ceef188f9cd708943d48c1259ebe84 (patch)
tree24014a47a676c5dc02d5e0b77cb5e4ac851af225 /tools/testing/selftests/rcutorture/bin/parse-console.sh
parenttorture: Print PID in hung-kernel diagnostic message (diff)
torture: Check for nul bytes in console output
When starting a new torture run while an old one is still running, both qemu processes can be outputting to the same console.out file. This can cause quite a bit of confusion, so this commit checks for this situation, which is normally indicated by nul bytes in the console output. Yes, if your new run uses up an exact number of blocks of the file, this check will be ineffective, but the odds are not bad. Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Reviewed-by: Pranith Kumar <bobby.prani@gmail.com>
Diffstat (limited to 'tools/testing/selftests/rcutorture/bin/parse-console.sh')
1 files changed, 4 insertions, 0 deletions
diff --git a/tools/testing/selftests/rcutorture/bin/parse-console.sh b/tools/testing/selftests/rcutorture/bin/parse-console.sh
index a0bde6c79456..f962ba4cf68b 100755
--- a/tools/testing/selftests/rcutorture/bin/parse-console.sh
+++ b/tools/testing/selftests/rcutorture/bin/parse-console.sh
@@ -32,6 +32,10 @@ title="$2"
. functions.sh
+if grep -Pq '\x00' < $file
+ print_warning Console output contains nul bytes, old qemu still running?
egrep 'Badness|WARNING:|Warn|BUG|===========|Call Trace:|Oops:' < $file | grep -v 'ODEBUG: ' | grep -v 'Warning: unable to open an initial console' > $T
if test -s $T