1#!/usr/bin/env bash 2# 3# Tests handling of colons in filenames (which may be confused with protocol 4# prefixes) 5# 6# Copyright (C) 2017 Red Hat, Inc. 7# 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. 12# 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. 17# 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/>. 20# 21 22# creator 23owner=mreitz@redhat.com 24 25seq="$(basename $0)" 26echo "QA output created by $seq" 27 28status=1 # failure is the default! 29 30# get standard environment, filters and checks 31. ./common.rc 32. ./common.filter 33 34# Needs backing file support 35_supported_fmt qcow qcow2 qed vmdk 36# This is the default protocol (and we want to test the difference between 37# colons which separate a protocol prefix from the rest and colons which are 38# just part of the filename, so we cannot test protocols which require a prefix) 39_supported_proto file 40 41echo 42echo '=== Testing plain files ===' 43echo 44 45# A colon after a slash is not a protocol prefix separator 46TEST_IMG="$TEST_DIR/a:b.$IMGFMT" _make_test_img 64M 47_rm_test_img "$TEST_DIR/a:b.$IMGFMT" 48 49# But if you want to be really sure, you can do this 50TEST_IMG="file:$TEST_DIR/a:b.$IMGFMT" _make_test_img 64M 51_rm_test_img "$TEST_DIR/a:b.$IMGFMT" 52 53 54echo 55echo '=== Testing relative backing filename resolution ===' 56echo 57 58BASE_IMG="$TEST_DIR/image:base.$IMGFMT" 59TOP_IMG="$TEST_DIR/image:top.$IMGFMT" 60 61TEST_IMG=$BASE_IMG _make_test_img 64M 62TEST_IMG=$TOP_IMG _make_test_img -b ./image:base.$IMGFMT 63 64# (1) The default cluster size depends on the image format 65# (2) vmdk only supports vmdk backing files, so it always reports the 66# format of its backing file as such (but neither it nor qcow 67# support the backing_fmt creation option, so we cannot use that to 68# harmonize the output across all image formats this test supports) 69TEST_IMG=$TOP_IMG _img_info | grep -ve 'cluster_size' -e 'backing file format' 70 71_rm_test_img "$BASE_IMG" 72_rm_test_img "$TOP_IMG" 73 74 75# Do another test where we access both top and base without any slash in them 76echo 77pushd "$TEST_DIR" >/dev/null 78 79BASE_IMG="base.$IMGFMT" 80TOP_IMG="file:image:top.$IMGFMT" 81 82TEST_IMG=$BASE_IMG _make_test_img 64M 83TEST_IMG=$TOP_IMG _make_test_img -b "$BASE_IMG" 84 85TEST_IMG=$TOP_IMG _img_info | grep -ve 'cluster_size' -e 'backing file format' 86 87_rm_test_img "$BASE_IMG" 88_rm_test_img "image:top.$IMGFMT" 89 90popd >/dev/null 91 92# Note that we could also do the same test with BASE_IMG=file:image:base.$IMGFMT 93# -- but behavior for that case is a bit strange. Protocol-prefixed paths are 94# in a sense always absolute paths, so such paths will never be combined with 95# the path of the overlay. But since "image:base.$IMGFMT" is actually a 96# relative path, it will always be evaluated relative to qemu's CWD (but not 97# relative to the overlay!). While this is more or less intended, it is still 98# pretty strange and thus not something that is tested here. 99# (The root of the issue is the use of a relative path with a protocol prefix. 100# This may always give you weird results because in one sense, qemu considers 101# such paths absolute, whereas in another, they are still relative.) 102 103 104# success, all done 105echo '*** done' 106rm -f $seq.full 107status=0 108