3 # Tests handling of colons in filenames (which may be confused with protocol
6 # Copyright (C) 2017 Red Hat, Inc.
8 # This program is free software; you can redistribute it and/or modify
9 # it under the terms of the GNU General Public License as published by
10 # the Free Software Foundation; either version 2 of the License, or
11 # (at your option) any later version.
13 # This program is distributed in the hope that it will be useful,
14 # but WITHOUT ANY WARRANTY; without even the implied warranty of
15 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
16 # GNU General Public License for more details.
18 # You should have received a copy of the GNU General Public License
19 # along with this program. If not, see <http://www.gnu.org/licenses/>.
23 owner
=mreitz@redhat.com
26 echo "QA output created by $seq"
28 status
=1 # failure is the default!
30 # get standard environment, filters and checks
34 # Needs backing file support
35 _supported_fmt qcow qcow2 qed vmdk
36 _unsupported_imgopts
"subformat=monolithicFlat" \
37 "subformat=twoGbMaxExtentFlat"
38 # This is the default protocol (and we want to test the difference between
39 # colons which separate a protocol prefix from the rest and colons which are
40 # just part of the filename, so we cannot test protocols which require a prefix)
44 echo '=== Testing plain files ==='
47 # A colon after a slash is not a protocol prefix separator
48 TEST_IMG
="$TEST_DIR/a:b.$IMGFMT" _make_test_img
64M
49 _rm_test_img
"$TEST_DIR/a:b.$IMGFMT"
51 # But if you want to be really sure, you can do this
52 TEST_IMG
="file:$TEST_DIR/a:b.$IMGFMT" _make_test_img
64M
53 _rm_test_img
"$TEST_DIR/a:b.$IMGFMT"
57 echo '=== Testing relative backing filename resolution ==='
60 BASE_IMG
="$TEST_DIR/image:base.$IMGFMT"
61 TOP_IMG
="$TEST_DIR/image:top.$IMGFMT"
63 TEST_IMG
=$BASE_IMG _make_test_img
64M
64 TEST_IMG
=$TOP_IMG _make_test_img
-b .
/image
:base.
$IMGFMT
66 # (1) The default cluster size depends on the image format
67 # (2) vmdk only supports vmdk backing files, so it always reports the
68 # format of its backing file as such (but neither it nor qcow
69 # support the backing_fmt creation option, so we cannot use that to
70 # harmonize the output across all image formats this test supports)
71 TEST_IMG
=$TOP_IMG _img_info |
grep -ve 'cluster_size' -e 'backing file format'
73 _rm_test_img
"$BASE_IMG"
74 _rm_test_img
"$TOP_IMG"
77 # Do another test where we access both top and base without any slash in them
79 pushd "$TEST_DIR" >/dev
/null
81 BASE_IMG
="base.$IMGFMT"
82 TOP_IMG
="file:image:top.$IMGFMT"
84 TEST_IMG
=$BASE_IMG _make_test_img
64M
85 TEST_IMG
=$TOP_IMG _make_test_img
-b "$BASE_IMG"
87 TEST_IMG
=$TOP_IMG _img_info |
grep -ve 'cluster_size' -e 'backing file format'
89 _rm_test_img
"$BASE_IMG"
90 _rm_test_img
"image:top.$IMGFMT"
94 # Note that we could also do the same test with BASE_IMG=file:image:base.$IMGFMT
95 # -- but behavior for that case is a bit strange. Protocol-prefixed paths are
96 # in a sense always absolute paths, so such paths will never be combined with
97 # the path of the overlay. But since "image:base.$IMGFMT" is actually a
98 # relative path, it will always be evaluated relative to qemu's CWD (but not
99 # relative to the overlay!). While this is more or less intended, it is still
100 # pretty strange and thus not something that is tested here.
101 # (The root of the issue is the use of a relative path with a protocol prefix.
102 # This may always give you weird results because in one sense, qemu considers
103 # such paths absolute, whereas in another, they are still relative.)