diff options
author | Steven Rostedt (Red Hat) <rostedt@goodmis.org> | 2015-02-03 21:45:13 +0100 |
---|---|---|
committer | Steven Rostedt <rostedt@goodmis.org> | 2015-02-03 21:45:13 +0100 |
commit | 7c2c49eceb79eb4738f38a00270830057b5bfb76 (patch) | |
tree | 8a2230889ffe2c2f657538cf694305abdb4c8ce9 /tools | |
parent | ktest: Cleanup terminal on dodie() failure (diff) | |
download | linux-7c2c49eceb79eb4738f38a00270830057b5bfb76.tar.xz linux-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')
-rwxr-xr-x | tools/testing/ktest/ktest.pl | 2 |
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"; |