1#!/bin/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_supported_os Linux 41 42echo 43echo '=== Testing plain files ===' 44echo 45 46# A colon after a slash is not a protocol prefix separator 47TEST_IMG="$TEST_DIR/a:b.$IMGFMT" _make_test_img 64M 48_rm_test_img "$TEST_DIR/a:b.$IMGFMT" 49 50# But if you want to be really sure, you can do this 51TEST_IMG="file:$TEST_DIR/a:b.$IMGFMT" _make_test_img 64M 52_rm_test_img "$TEST_DIR/a:b.$IMGFMT" 53 54 55echo 56echo '=== Testing relative backing filename resolution ===' 57echo 58 59BASE_IMG="$TEST_DIR/image:base.$IMGFMT" 60TOP_IMG="$TEST_DIR/image:top.$IMGFMT" 61 62TEST_IMG=$BASE_IMG _make_test_img 64M 63TEST_IMG=$TOP_IMG _make_test_img -b ./image:base.$IMGFMT 64 65# The default cluster size depends on the image format 66TEST_IMG=$TOP_IMG _img_info | grep -v 'cluster_size' 67 68_rm_test_img "$BASE_IMG" 69_rm_test_img "$TOP_IMG" 70 71 72# Do another test where we access both top and base without any slash in them 73echo 74pushd "$TEST_DIR" >/dev/null 75 76BASE_IMG="base.$IMGFMT" 77TOP_IMG="file:image:top.$IMGFMT" 78 79TEST_IMG=$BASE_IMG _make_test_img 64M 80TEST_IMG=$TOP_IMG _make_test_img -b "$BASE_IMG" 81 82TEST_IMG=$TOP_IMG _img_info | grep -v 'cluster_size' 83 84_rm_test_img "$BASE_IMG" 85_rm_test_img "image:top.$IMGFMT" 86 87popd >/dev/null 88 89# Note that we could also do the same test with BASE_IMG=file:image:base.$IMGFMT 90# -- but behavior for that case is a bit strange. Protocol-prefixed paths are 91# in a sense always absolute paths, so such paths will never be combined with 92# the path of the overlay. But since "image:base.$IMGFMT" is actually a 93# relative path, it will always be evaluated relative to qemu's CWD (but not 94# relative to the overlay!). While this is more or less intended, it is still 95# pretty strange and thus not something that is tested here. 96# (The root of the issue is the use of a relative path with a protocol prefix. 97# This may always give you weird results because in one sense, qemu considers 98# such paths absolute, whereas in another, they are still relative.) 99 100 101# success, all done 102echo '*** done' 103rm -f $seq.full 104status=0 105