aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/ktest
diff options
context:
space:
mode:
authorSteven Rostedt (Red Hat) <rostedt@goodmis.org>2015-02-03 15:45:13 -0500
committerSteven Rostedt <rostedt@goodmis.org>2015-02-03 15:45:13 -0500
commit7c2c49eceb79eb4738f38a00270830057b5bfb76 (patch)
tree8a2230889ffe2c2f657538cf694305abdb4c8ce9 /tools/testing/ktest
parentktest: Cleanup terminal on dodie() failure (diff)
downloadlinux-dev-7c2c49eceb79eb4738f38a00270830057b5bfb76.tar.xz
linux-dev-7c2c49eceb79eb4738f38a00270830057b5bfb76.zip
ktest: Place quotes around item variable
Seems that some of the new console logic causes doprint to possibly get evaluated. When printing a commit message that contains parenthesis, it fails with a shell parsing error. This gets fixed when we add quotes around the $item variable, and prevent it from being evaluated by any shell commands. Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'tools/testing/ktest')
-rwxr-xr-xtools/testing/ktest/ktest.pl2
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/testing/ktest/ktest.pl b/tools/testing/ktest/ktest.pl
index 840803b3cd41..d08e214ec6e7 100755
--- a/tools/testing/ktest/ktest.pl
+++ b/tools/testing/ktest/ktest.pl
@@ -3447,7 +3447,7 @@ sub patchcheck {
my $sha1 = $item;
$sha1 =~ s/^([[:xdigit:]]+).*/$1/;
- doprint "\nProcessing commit $item\n\n";
+ doprint "\nProcessing commit \"$item\"\n\n";
run_command "git checkout $sha1" or
die "Failed to checkout $sha1";