diff options
author | Lucas Bates | 2018-03-26 16:46:14 +0200 |
---|---|---|
committer | David S. Miller | 2018-03-27 16:52:07 +0200 |
commit | cd464197f2378499db134d6c44af3b4e3c0c14b5 (patch) | |
tree | ee5e050e83da80c020d399523d7b8f8c1b2998e1 /fs/reiserfs/fix_node.c | |
parent | tipc: tipc_node_create() can be static (diff) | |
download | kernel-qcow2-linux-cd464197f2378499db134d6c44af3b4e3c0c14b5.tar.gz kernel-qcow2-linux-cd464197f2378499db134d6c44af3b4e3c0c14b5.tar.xz kernel-qcow2-linux-cd464197f2378499db134d6c44af3b4e3c0c14b5.zip |
tc-testing: Correct compound statements for namespace execution
If tdc is executing test cases inside a namespace, only the
first command in a compound statement will be executed inside
the namespace by tdc. As a result, the subsequent commands
are not executed inside the namespace and the test will fail.
Example:
for i in {x..y}; do args="foo"; done && tc actions add $args
The namespace execution feature will prepend 'ip netns exec'
to the command:
ip netns exec tcut for i in {x..y}; do args="foo"; done && \
tc actions add $args
So the actual tc command is not parsed by the shell as being
part of the namespace execution.
Enclosing these compound statements inside a bash invocation
with proper escape characters resolves the problem by creating
a subshell inside the namespace.
Signed-off-by: Lucas Bates <lucasb@mojatatu.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'fs/reiserfs/fix_node.c')
0 files changed, 0 insertions, 0 deletions